-
Notifications
You must be signed in to change notification settings - Fork 721
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
Eclipse 2021-12 crashes very often after switching from jdk 11 to jdk 17 #14489
Comments
The dump is 300Mb as ziped file, can i attach it here ? |
You can try, as long as github accepts it. |
javacore.20220211.110201.11772.0002.txt |
We are using lombok and i have found a similar error |
The dump file is to big to upload ... |
You can use a file sharing service for the system dump. |
@0xdaryl fyi The javacore shows
|
@c-koell : in the same directory where you found the core and javacore, can you see if there are any "jitdump" files produced? Could you upload those? If this crashes consistently in the same place, could you add the following to the JVM command-line and re-run please? (this will enable JIT compile tracing for that method and place the info in a file called
Please upload the @BradleyWood : once a system dump and hopefully trace file is made available could you start looking into this crash please? |
Looks to be the same issue as reported to Project Lombok on linux with JDK11 0.29. @c-koell Are you sure this only happens on JDK17, and is it intermittent? You can also set TR_Options environment variable if your jvm is invoked via maven or some other build system.
You could also try to exclude that method from compilation as a work-around.
I wasn't able to reproduce a crash with a trivial example program using project lombok. |
I have seen the crash also on jdk11 but very rarly. I have a workspace where i can easily reproduce the crash. I have attached all files under this fileshare url. Please use "jwgngGsgNs" as password. If i use '-Xjit:{BubblingConfigurationResolver.resolve}(tracefull,traceGlobalVP,log=tracevplog.txt)' the crash does not occur |
Did you include the asterisks ( |
Dumping the backtrace...
|
Sorry i have accidentally closed this issue :-) |
I have used |
Based on debugging information from core file, applyGlobalConstraints() fails join two constraints which causes a failure when adding the global constraint. At TR::VPConstraint::intersect(...) (called from applyGlobalConstraints(...) ) Therefore, we end up at TR::VPClass::intersect1(...) Since both constraints are not a class object and one is a VPNullObject, we end up here. At this point, (this (VPClass))->_presense is a VPNonNullObject so the call to isNonNullObject() returns true. Therefore the result of the intersection is null. |
@c-koell I was wondering if you could provide some detailed instructions to reproduce the issue. |
Hi @BradleyWood ... really nothing special. After opening the workspace i right click on the project and execute "Maven -> Update Project" |
@c-koell I tried the following but couldn't reproduce like that. Here are the steps I tried, correct me if I missed something.
Perhaps its something specific to your project that makes the issue more apparent. Also, when the JIT crashed, the problematic method was recompiled with tracing on for diagnostic purposes. However, it did not crash during recompilation. We are aware of some issues where tracing can impact the reproducability of bugs like this. Also observed some strange differences in inlining when the crash occurs. Maybe you could try the following JVM options and hopefully reproduce the issue with tracing.
|
Unfortunately at the moment i see no more crash while opening my eclipse workspace .... hmm i don't know what i have changed ... |
I had today another crash. Unfortionally without trace enabled but maybe the trace helps you. I have attached the new trace (crash-16.03.zip) under this fileshare url. Please use "jwgngGsgNs" as password. |
Sorry the above link has expired. New new link is https://tbox.tirol.gv.at/index.php/s/C9LoR6S3ntxQSja with "JKoRmPZQ3t" as password |
Now i have a crash with trace enabled. See the File crash_with_trace_17.03.zip in the described file share link above. |
I will take a look |
@BradleyWood any news here ? It's really annoying when eclipse crashes really often :-( |
You should be able to prevent the crash with these options:
The trace logs are suspiciously large, I will need time to consult with colleagues. eclipse/omr#6356 should also fix the issue, but there is concern that it will hide a deeper issue. |
I'm tentatively putting this into the 0.33 milestone plan. |
In the javacore file, these seem to contradict each other:
Also, |
I'm looking at a Java8 crash with a null 'this' passed to intersect() that looks like it came from the return value of a prior call to applyGlobalConstraints. I don't know if I can track back to the constraint that was passed to applyGlobalConstraints to see if it was also null, but I'll give it a go. (method was being compiled at very-hot, having previously succeeded at cold, warm and hot) Crash stack in my case is very similar, but not quite identical:
|
I located the constraint instance passed as a parameter to applyGlobalConstraints and it appears to be a VPNullObject, which matches up with Brad's comments in #14489 (comment) |
@BradleyWood Any new news on this one? |
This one has been very difficult to root-out by looking at the trace logs, and I can't reproduce the issue. We have enlisted Vijay's help on this. |
Java -version output
openjdk 11 ->
openjdk version "11.0.14" 2022-01-18
IBM Semeru Runtime Open Edition 11.0.14.0 (build 11.0.14+9)
Eclipse OpenJ9 VM 11.0.14.0 (build openj9-0.30.0, JRE 11 Windows 10 amd64-64-Bit Compressed References 20220128_296 (JIT enabled, AOT enabled)
openjdk 17 ->
openjdk version "17.0.2" 2022-01-18
IBM Semeru Runtime Open Edition 17.0.2.0 (build 17.0.2+8)
Eclipse OpenJ9 VM 17.0.2.0 (build openj9-0.30.0, JRE 17 Windows 10 amd64-64-Bit Compressed References 20220128_95 (JIT enabled, AOT enabled)
Summary of problem
Nothing special .. After working some time in eclipse it crashes ...
Diagnostic files
I will attach the generated dump files from the crash.
The text was updated successfully, but these errors were encountered: