| Summary: | Eclipse freezes and eventually crashes while opening java class | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | [Eclipse Project] JDT | Reporter: | Joris Kinable <j.kinable> | ||||||||
| Component: | Core | Assignee: | JDT-Core-Inbox <jdt-core-inbox> | ||||||||
| Status: | CLOSED WONTFIX | QA Contact: | |||||||||
| Severity: | normal | ||||||||||
| Priority: | P3 | CC: | jarthana, loskutov, sasikanth.bharadwaj, stephan.herrmann | ||||||||
| Version: | 4.4.2 | ||||||||||
| Target Milestone: | --- | ||||||||||
| Hardware: | PC | ||||||||||
| OS: | Linux | ||||||||||
| Whiteboard: | stalebug | ||||||||||
| Attachments: |
|
||||||||||
|
Description
Joris Kinable
Please create JVM dump at the time CPU is fully loaded. $jps -l 123123 sun.tools.jps.Jps 424242 /opt/eclipse/plugins/org.eclipse.equinox.* $jstack 424242 > JVM_dump.log Btw your error log shows: java.lang.OutOfMemoryError: GC overhead limit exceeded Try to increase heap to 4GB: change your eclipse.ini from -Xmx1024m to -Xmx4g - will it help? But the dump is needed to understand what is causing such high memory consumption. Created attachment 252507 [details]
JVM dump log 1
Created attachment 252508 [details]
JVM dump log 2
(In reply to Andrey Loskutov from comment #2) > Btw your error log shows: java.lang.OutOfMemoryError: GC overhead limit > exceeded > Try to increase heap to 4GB: change your eclipse.ini from -Xmx1024m to > -Xmx4g - will it help? But the dump is needed to understand what is causing > such high memory consumption. I've tried your suggestion. It doesn't help though: -eclipse doesn't respond -my system becomes unusable As per your request I've added 2 dumps taken sequentially. I hope this helps. Thank you for your effort! Moving to JDT for investigation. The stack contains lot of org.eclipse.jdt.internal.compiler.lookup.* methods Similar to bug 456924 with these differences: we don't see a StackOverflowError just a very busy computer, and: we're stuck with PTB and CaptureBinding18 vs. PTB and CaptureBinding in the other bug. Reproduction using the linked github repo should point us directly to the root cause. Anyone? I've moved the project repository containing the code to reproduce this issue to: https://github.com/jkinable/jorlib/tree/eclipseBug The link pointing to https://github.com/jkinable/jorlib/tree/development at the beginning of this thread is no longer valid. This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. As such, we're closing this bug. If you have further information on the current state of the bug, please add it and reopen this bug. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant. -- The automated Eclipse Genie. |