-
Notifications
You must be signed in to change notification settings - Fork 737
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
testSoftMxDisclaimMemory_GC_3_FAILED : Segmentation error vmState=0x0002000f #14396
Comments
This issue looks like a duplicate of #14382 |
The crash occur an attempt to scan mixed object, one of slots points to the "hole":
|
Also I noticed pointer to |
Another like #14399 which was closed as a dup of this. https://openj9-jenkins.osuosl.org/job/Test_openjdk11_j9_extended.functional_x86-64_linux_Nightly_testList_1/189 - cent6-x64-6
|
yes, it is the same issue. Just for record:
|
https://openj9-jenkins.osuosl.org/job/Test_openjdk17_j9_extended.functional_x86-64_linux_Nightly_testList_0/135 - ub20-x86-1
|
As per #14382 (comment) setting as a blocker. |
Closing one is fine, but the remaining issue should be in the 0.31 milestone plan. |
1, The issue can not be reproduced by grinder x 100 with single test(testSoftMxLocal_LP4k_3 or testSoftMxDisclaimMemory_GC_3) on both java17 and java18, but can be reproduced with whole test list(extended.funtional test_list_0, 2/10)on java 17 and java 18, never been reproduced on Java 8(axxon). 2, The tests are running under extreme corner case for balanced GC(-Xmx1024m -Xsoftmx512m -Xmn1m, -XX:+DisclaimVirtualMemory, regionsize = 512K eden region count = 2, test case uses a couple of large arrays, the largest array has 40 leaf regions, it cost more than half GCs did almost nothing, because all of two eden regions had been allocated for arraylet leaves, then there is zero region for collection set), not sure if the tests intend to check this env. 3, these tenure regions were marked and swept by the last GMP, but after the GMP the region haven't been used as survivor, crash happened, GC tried to scan a reference point to freeEntry header, the reference might come from remembered set or live object, looks like GMP missed to mark some traceable object, but no clue is found to cause the case yet. 4,It started failing after Jan 26th, 2022, it seems a regression. during January there was only one related GC change, (eclipse-omr/omr#6303, merged on Jan 20), it might not be related, but trying to create a latest build exclude the change, see if it is possible that eclipse-omr/omr#6303 trigger the issue. the latest personal build with the change |
https://openj9-jenkins.osuosl.org/job/Test_openjdk17_j9_extended.functional_x86-64_linux_Nightly_testList_0/137 - ub20-x86-1
|
both personal build with/without allocation hint change have similar failure cases, so this issue wasn't cause by allocation hint change. look like the failure started between Jan 26 and Jan 27 for internal build. the latest personal build with allocation hint change(eclipse-omr/omr#6303) |
uodate: |
https://openj9-jenkins.osuosl.org/job/Test_openjdk11_j9_extended.functional_x86-64_linux_Nightly_testList_0/194 - ub16x64j98
|
@LinHu2016 repeated testing to narrow down the problem and has provided diffs between last good and first bad builds: |
https://openj9-jenkins.osuosl.org/job/Test_openjdk17_j9_extended.functional_x86-64_linux_Nightly_testList_0/140 - ub20-x86-1 |
https://openj9-jenkins.osuosl.org/job/Test_openjdk17_j9_extended.functional_x86-64_linux_Nightly_testList_0/141 - ub20-x86-1 https://openj9-jenkins.osuosl.org/job/Test_openjdk17_j9_extended.functional_x86-64_linux_Nightly_testList_1/141 - ub16x64j96 |
I have kind narrowed down the issue, java 17 grinder x10 |
That means #14471 didn't fix it, it's still failing in the nightly build last night as per #14396 (comment) |
The failures continue to occur but I'm not going to keep reporting them. |
Is there any update on fixing this problem? |
fixing #14577, still need to run grinders for confirming. |
Failure link
From an internal build
job/Test_openjdk18_j9_extended.functional_x86-64_linux_testList_0/3/
(ub20x64rt3-8
):Rerun in Grinder - Change TARGET to run only the failed test targets.
Optional info
Failure output (captured from console output)
fyi @dmitripivkine
The text was updated successfully, but these errors were encountered: