When 'Retrieve' IntelliJ shutdown
Issue #1745
resolved
Hello,
I have a problem with IntelliJ when I try the option ‘Retrieve’ (Illuminated Cloud). After selected 'Retrieve' IntelliJ automatically shutdowns (closed).
I don’t what happening here, but maybe someone recognise this issue and can help me with the right solution?
This is a part of the message.
A fatal error has been detected by the Java Runtime Environment:
Internal Error (loopnode.hpp:769), pid=66981, tid=43267
guarantee(n != NULL) failed: No Node.
JRE version: OpenJDK Runtime Environment JBR-11.0.8.10-944.34-jcef (11.0.8+10) (build 11.0.8+10-b944.34)
Java VM: OpenJDK 64-Bit Server VM JBR-11.0.8.10-944.34-jcef (11.0.8+10-b944.34, mixed mode, tiered, compressed oops, concurrent mark sweep gc, bsd-amd64)
No core dump will be written. Core dumps have been disabled. To enable core dumping, try "ulimit -c unlimited" before starting Java again
If you would like to submit a bug report, please visit:
https://bugreport.java.com/bugreport/crash.jsp
--------------- S U M M A R Y ------------
Command Line: -Xms128m -Xmx2048m -XX:ReservedCodeCacheSize=240m -XX:+UseCompressedOops -Dfile.encoding=UTF-8 -XX:+UseConcMarkSweepGC -XX:SoftRefLRUPolicyMSPerMB=50 -ea -XX:CICompilerCount=2 -Dsun.io.useCanonPrefixCache=false -Djava.net.preferIPv4Stack=true -Djdk.http.auth.tunneling.disabledSchemes="" -XX:+HeapDumpOnOutOfMemoryError -XX:-OmitStackTraceInFastThrow -Djdk.attach.allowAttachSelf -Dkotlinx.coroutines.debug=off -Djdk.module.illegalAccess.silent=true -XX:ErrorFile=/Users/ohr001/java_error_in_idea_%p.log -XX:HeapDumpPath=/Users/ohr001/java_error_in_idea.hprof -Djb.vmOptionsFile=/Users/ohr001/Library/Application Support/JetBrains/IdeaIC2020.2/idea.vmoptions -Didea.paths.selector=IdeaIC2020.2 -Didea.executable=idea -Didea.platform.prefix=Idea -Didea.vendor.name=JetBrains -Didea.home.path=/Applications/IntelliJ IDEA CE.app/Contents
Host: MacBookPro15,1 x86_64 2200 MHz, 12 cores, 16G, Darwin 19.4.0
Time: Mon Oct 26 12:37:28 2020 CET elapsed time: 89 seconds (0d 0h 1m 29s)
--------------- T H R E A D ---------------
Current thread (0x00007fa99581c800): JavaThread "C2 CompilerThread0" daemon [_thread_in_native, id=43267, stack(0x000070000313a000,0x000070000323a000)]
Current CompileTask:
C2: 89361 30329 % ! 4 com.illuminatedcloud.intellij.builder.BuildOptionsDialog$2::run @ 4921 (7952 bytes)
Stack: [0x000070000313a000,0x000070000323a000], sp=0x000070000322cd50, free space=971k
Native frames: (J=compiled Java code, A=aot compiled Java code, j=interpreted, Vv=VM code, C=native code)
V [libjvm.dylib+0x745948] _ZN7VMError14report_and_dieEiPKcS1_P13__va_list_tagP6ThreadPhPvS7_S1_im+0x660
V [libjvm.dylib+0x746045] _ZN7VMError14report_and_dieEP6ThreadPvPKciS4_S4_P13__va_list_tag+0x47
V [libjvm.dylib+0x26232c] _Z15report_vm_errorPKciS0_S0_z+0xa9
V [libjvm.dylib+0x5167c4] _ZNK14PhaseIdealLoop8has_nodeEP4Node+0x44
V [libjvm.dylib+0x50643f] _ZNK14PhaseIdealLoop8get_loopEP4Node+0x2f
Comments (5)
-
repo owner
-
repo owner
- changed status to resolved
I'm going to resolve this since these JVM args do seem to have addressed the issue for everyone so far, but if they don't for you, please reopen with additional details.
-
reporter
Hi Scott,
Thanks for you help, it works.
I appreciated your quick reaction.Have a nice evening!
-
repo owner
Glad to hear that did it for you! Note that I have seen perhaps 2-3 shutdowns/hard crashes of IntelliJ IDEA even since adding those arguments--even just using the Java IDE and not Illuminated Cloud--but that's over the past 2-3 months, so a VAST improvement. Just wanted to let you know that this workaround is greatly effective but doesn't seem to be 100% perfect. However, if you do see it happen with any frequency, please let me know so I can raise it with JetBrains.
-
repo owner
- removed component
Removing component: IntelliJ IDEA (automated comment)
- Log in to comment
I've heard about similar from a few other users. It appears that there may be an issue with the JetBrains OpenJDK on certain Intel hardware. You can find out more here:
https://youtrack.jetbrains.com/issue/JBR-2310
I have a Surface Laptop 3 and had also been experiencing numerous crashes of both the IDE and even the entire OS.
The solution for the problem cited above is to get an OS update that includes Intel microcode 50, but that's not available for all OSes. It's out for Mac and some Linux distributions, but I don't think any Windows machines have it yet (including my Surface Laptop 3). However, I've heard about instances of this type of crash from users not even on this hardward.
The workaround seems to be to add these JVM arguments for the IDE:
using Help>Edit Custom VM Options. Please try that and let me know if it doesn't resolve the issue for you. I'll also let JetBrains know that another user is seeing this now.