-
Notifications
You must be signed in to change notification settings - Fork 729
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
Test-extended.system-JDK8-win_x86 SharedClasses_Softmx_UpDown_0 crash vmState=0x00000000 MethodSorter.getDeclaredMethods #4201
Comments
5x grinder passed |
Didn't see the results before the grinder was removed. Try again |
50x grinder passed. I think I'll close this. We can reopen if the problem is seen again. |
Another occurrence https://ci.eclipse.org/openj9/job/Test-extended.system-JDK8-win_x86/149
|
It's possible; however if the issue is a missing relocation, then the SVM wouldn't really help since it's main purpose is validation. Given that this is windows, it's possible that the SVM is enabled for this compile (if it happened after startup). |
@dsouzai so is this something that should be looked at as part of the SVM migration then? |
Well there's three options here:
Of the AOT bugs we've run into thus far, they've almost always been an existing bug that we just never ran into before, or existing bug now exposed because of the new code paths under AOT that are now being exercised thanks to the SVM. So I guess in terms of "something that should be looked at as part of the SVM migration then", I'd say it's worth noting that the SVM migration is likely going to expose existing bugs, but I wouldn't necessarily tie AOT bugs to the SVM. |
I won't have time this week to take a look at this, but I'll take a look next week; I've assigned it to me so it doesn't fall under the radar. |
https://ci.eclipse.org/openj9/job/Test-extended.system-JDK11-linux_x86-64_cmprssptrs/176
|
Note that last one is an assert and not a crash. |
Well, more reason to believe a missed relocation :). I didn't have time to look at this issue this week, but I'm definitely going to next week. Also I'm really glad this isn't a Windows only issue; I can try and reproduce this using at linux job. EDIT: There's a core!! |
https://ci.eclipse.org/openj9/job/Test-extended.system-JDK8-win_x86/159
|
Yes, the jobs do save the core. |
This is the output from the assert:
From GDB:
Looking at the stackslots:
The bad O-slot comes from rbx, which got its value from
This looks very similar to #4138 (comment); this is also a warm AOT'd body:
I believe that this bug is caused by the problem described in #4621 . As such, it should be fixed by #4723 |
Running the testing here https://ci.eclipse.org/openj9/view/Pipelines/job/Pipeline-Build-Test-All/401/ |
Test passed. Doing a 5x grinder as well https://ci.eclipse.org/openj9/view/Test/job/Test-Grinder/271/ |
5x grinder passed. |
This problem still occurs. The nightly system tests weren't running for a while, but they are running again now. https://ci.eclipse.org/openj9/job/Test-extended.system-JDK8-win_x86/176/
|
Opened #4892 |
I suppose this doesn't need to be fixed in the 0.13 release since it fails on Windows 32-bit, which isn't supported by Java 12. The 0.13 release only includes Java 12. |
https://ci.eclipse.org/openj9/job/Test-extended.system-JDK8-win_x86/126/
The text was updated successfully, but these errors were encountered: