Community
Participate
Working Groups
Created attachment 197229 [details] eclipse config + error logs Eclipse crashes with no apparent trigger while editing or browsing a Mylyn task. See logs for segmentation error files and Eclipse configuration.
That looks like this JVM bug: http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=2210012 # Internal Error (c1_Optimizer.cpp:271), pid=6944, tid=8260 # guarantee(x_compare_res != Constant::not_comparable) failed: incomparable constants in IfOp Current CompileTask: C1:2402912 2993 org.eclipse.mylyn.tasks.ui.AbstractTaskHyperlinkDetector.getTaskRepository(Lorg/eclipse/jface/text/ITextViewer;)Lorg/eclipse/mylyn/tasks/core/TaskRepository; (120 bytes ) vm_info: Java HotSpot(TM) Client VM (20.0-b11) for windows-x86 JRE (1.6.0_25-b06), built on Apr 14 2011 01:04:32 by "java_re" with MS VC++ 7.1 (VS2003)
*** Bug 349539 has been marked as a duplicate of this bug. ***
Please try updating to the latest JVM and reopen if you are still seeing the crashes.
I am seeing this too. Updated to JRE version: 6.0_26-b03 but still the same :(
I can't figure out if/when the fix is supposed to have been released. On the Oracle bug it says "Release Fixed 7(b143)", but I can't find anything in the past release notes
(In reply to comment #5) > I can't figure out if/when the fix is supposed to have been released. On the > Oracle bug it says "Release Fixed 7(b143)", but I can't find anything in the > past release notes Oh, it appears it's only fixed in Java 7 I am running with the -server (server compiler) as there seem to be people saying that might be a workaround...
Switching to Java 7 seemed to have resolved this for me
(In reply to comment #7) > Switching to Java 7 seemed to have resolved this for me I had the same problem with Eclipse 3.7 on a Windows 7 x64 machine using the 32-Bit JRE version 1.6.0_27-b07. Switching to the 32-Bit JRE version 1.7.0-b147 resolved the problem also for me.
*** Bug 397281 has been marked as a duplicate of this bug. ***
*** Bug 387592 has been marked as a duplicate of this bug. ***
A last update (as promised in Bug 387592) - since changing my JVM to Java 7, the problem has gone.