Frequent crashes of GoLand on Ubuntu 22.04
I am currently using GoLand 2022.1, and I have been experiencing very frequent crashes lately after updating to Ubuntu 22.04. Are there known issues or perhaps new patches that could help to alleviate this problem?
Example info from my crash log:
#
# A fatal error has been detected by the Java Runtime Environment:
#
# SIGSEGV (0xb) at pc=0x00007ff0341b9f84, pid=9615, tid=9669
#
# JRE version: OpenJDK Runtime Environment JBR-11.0.14.1.1-2043.25-jcef (11.0.14.1+1) (build 11.0.14.1+1-b2043.25)
# Java VM: OpenJDK 64-Bit Server VM JBR-11.0.14.1.1-2043.25-jcef (11.0.14.1+1-b2043.25, mixed mode, tiered, compressed oops, g1 gc, linux-amd64)
# Problematic frame:
# V [libjvm.so+0x7b9f84] void G1ScanObjsDuringUpdateRSClosure::do_oop_work<unsigned int>(unsigned int*)+0x74
#
# Core dump will be written. Default location: Core dumps may be processed with "/usr/share/apport/apport %p %s %c %d %P %E" (or dumping to [REDACTED]/core.9615)
#
# If you would like to submit a bug report, please visit:
# https://bugreport.java.com/bugreport/crash.jsp
#
Please sign in to leave a comment.
Please, collect the IDE logs via Help | Collect Logs and Diagnostic Data, upload them to https://uploads.jetbrains.com/ and provide its ID.
Sure, here it is:
Upload id: 2022_05_06_CwfRHZ7by8Zs8oib (file: goland-logs-20220506-16434317066488166928403118.zip)
Can you experience these crashes on the 2021.3.5 version of GoLand (https://www.jetbrains.com/go/download/other.html)?
Yes, it still keeps crashing, not sure if it's getting worse or not... From what I notice though, the crashes usually happen when I try to edit rather large files/packages. Don't think this is a memory issue since I still have quite a lot of free memory available, but not sure if it's perhaps caused by a config somewhere that limits the memory utilization.
Does increasing memory for the IDE via Help | Change Memory Settings help? Can you reproduce it constantly by refactoring large packages? What kind of refactoring did you invoke?
Ah, I recently managed to figure out the issue. It turns out that I had a problem with my RAM frequency configuration, where the automatic setting configured upon enabling the XMP profile was too high and further caused issues for processes that perform memory-intensive tasks. After lowering the value, the crashes don't seem to happen anymore. Thanks for your help so far though!