OpenJDK 64-Bit Server VM warning: Option UseConcMarkSweepGC was deprecated in version 9.0 and will likely be removed in a future release. # # A fatal error has been detected by the Java Runtime Environment: # # EXCEPTION_ACCESS_VIOLATION (0xc0000005) at pc=0x00007ff873eb648c, pid=19896, tid=19372 # # JRE version: (11.0.7+10) (build ) # Java VM: OpenJDK 64-Bit Server VM (11.0.7+10-b765.64, mixed mode, tiered, compressed oops, concurrent mark sweep gc, windows-amd64) # Problematic frame: # V [jvm.dll+0x64648c] # # No core dump will be written. Minidumps are not enabled by default on client versions of Windows # # An error report file with more information is saved as: # C:\Users\xx\java_error_in_RIDER_19896.log # # If you would like to submit a bug report, please visit: # http://bugreport.java.com/bugreport/crash.jsp #
I have the same problem as Dave. (Not sure if Michaelb's problem is the same or not, though.) Just updated to Rider 2020.1.3 and opening the editor shows no signs of it starting. Running rider.bat shows the same EXCEPTION_ACCESS_VIOLATION. The log says:
# # A fatal error has been detected by the Java Runtime Environment: # # EXCEPTION_ACCESS_VIOLATION (0xc0000005) at pc=0x00007ffb4ff3648c, pid=24864, tid=24612 # # JRE version: (11.0.7+10) (build ) # Java VM: OpenJDK 64-Bit Server VM (11.0.7+10-b765.64, mixed mode, tiered, compressed oops, concurrent mark sweep gc, windows-amd64) # Problematic frame: # V [jvm.dll+0x64648c] # # No core dump will be written. Minidumps are not enabled by default on client versions of Windows # # If you would like to submit a bug report, please visit: # http://bugreport.java.com/bugreport/crash.jsp #
Current thread (0x0000027efaba7000): JavaThread "Unknown thread" [_thread_in_vm, id=24612, stack(0x000000a1c2200000,0x000000a1c2300000)]
Stack: [0x000000a1c2200000,0x000000a1c2300000], sp=0x000000a1c22ff440, free space=1021k Native frames: (J=compiled Java code, j=interpreted, Vv=VM code, C=native code) V [jvm.dll+0x64648c] V [jvm.dll+0x1c5465] V [jvm.dll+0x2c2170] V [jvm.dll+0x2c15db] V [jvm.dll+0x58e3a1] V [jvm.dll+0x589392] V [jvm.dll+0x6f1cf0] V [jvm.dll+0x355909] V [jvm.dll+0x6d42ae] V [jvm.dll+0x3bda13] V [jvm.dll+0x3bfc51] C [jli.dll+0x5363] C [ucrtbase.dll+0x20e82] C [KERNEL32.DLL+0x17bd4] C [ntdll.dll+0x6ce51]
Installing 2020.1.4 from the website resolved the issue. Not sure what's different between downloading 2020.1.4 from the website and doing the in-editor upgrade on 2020.1.3 (which I believe said upgrade to 2020.1.3 not 2020.1.4... although I could be wrong).
for some long searching, I found how to solve this issue. I tried both method, first was reinstall IDE, but it didn't work still. Second was installing .NET Framework 4.8 Developer Pack. After that program works as well as before. Maybe it would help You to repair this problem. There I posting link to install Developer Pack : https://dotnet.microsoft.com/download/dotnet-framework/thank-you/net48-developer-pack-offline-installer.
Installing the latest Rider (2020.1.4) from the Download page resolved the issue for me. Make sure you uninstall the older version after installing the new version.
I updated today and cannot open IDE
rider.bat:
I have the same problem as Dave. (Not sure if Michaelb's problem is the same or not, though.) Just updated to Rider 2020.1.3 and opening the editor shows no signs of it starting. Running rider.bat shows the same EXCEPTION_ACCESS_VIOLATION. The log says:
Installing 2020.1.4 from the website resolved the issue. Not sure what's different between downloading 2020.1.4 from the website and doing the in-editor upgrade on 2020.1.3 (which I believe said upgrade to 2020.1.3 not 2020.1.4... although I could be wrong).
I have the exact same issue. I did the in-editor upgrade and it wouldn't start again.
Same issue. The IDE won't start after upgrade.
Hi everyone,
for some long searching, I found how to solve this issue. I tried both method, first was reinstall IDE, but it didn't work still. Second was installing .NET Framework 4.8 Developer Pack. After that program works as well as before. Maybe it would help You to repair this problem. There I posting link to install Developer Pack : https://dotnet.microsoft.com/download/dotnet-framework/thank-you/net48-developer-pack-offline-installer.
Hello there!
Thanks for your request! If you use Rider 2020.1.3, please try updating it to the latest version: https://www.jetbrains.com/rider/download. If the issue didn’t solve, please, collect and share all Rider logs collected right after crashing. Here is a guide about how to find logs: https://rider-support.jetbrains.com/hc/en-us/articles/360001079770-How-to-collect-Rider-logs-?
Please attach them to a new support request. If the file size is bigger than 20MB, please use this how-to.
It is worth noting that there was an issue in 2020.1.4 when everyone who updated Rider using patch cannot start it: RIDER-47292. Please use a full installer (https://www.jetbrains.com/rider/download/) or Toolbox app (https://www.jetbrains.com/toolbox-app/) as a workaround.
Installing the latest Rider (2020.1.4) from the Download page resolved the issue for me. Make sure you uninstall the older version after installing the new version.
I got this to stop happening on 2020.3 by uninstalling my JRE and installing the exact version mentioned in the error.
OpenJDK 64-Bit Server VM (11.0.7+10-b765.64)
Jetbrains may want to look into this bottleneck.
Had this same issue, fixed by installing old Rider 2020.3 (uninstalled Rider 2020.3.2 first)