Community
Participate
Working Groups
Build Identifier: 20110916-0149 Eclipse is *extremely* unstable on MacOS (10.7.2) with a variety of JVMs, including 1.6.0 and 1.7.0 dev preview. there is no apparent pattern to the tool usage that causes the crash, however the top of the stack trace is *always* the same in: org.eclipse.swt.internal.cocoa.OS.objc_msgSend_bool ... Reproducible: Always Steps to Reproduce: 1. start eclipse 2. open a Java project, edit some source code for a few minutes ... 3. crash, lose all your edits since you last saved the source...
Created attachment 209848 [details] text file of JVM stack trace/dump
Created attachment 209866 [details] another stack trace of the problem... occured immediately after Eclipse unmapped a popup "quick tip" window while in the Java text editor....
Created attachment 209867 [details] yet another ... I promise to stop now ...
Created attachment 228536 [details] Another instance of this crash. I also experienced this type of bad access (on [super _wantsRevealovers]) immediately after a tooltip was displayed.
(In reply to comment #4) > I also experienced this type of bad access (on [super _wantsRevealovers]) _wantsRevealovers seems different, it's bug 372952.
This is difficult to investigate without steps (I know you said there weren't any), and also because there have not been similar reports logged by others. I notice that you were using Eclipse 3.7.1; can you try moving up to Eclipse 4.3 (released today) and see if it seems to help? There have been lots of bug fixes in the interim, so it's possible that your case may be affected.
*** Bug 364416 has been marked as a duplicate of this bug. ***
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. If you have further information on the current state of the bug, please add it. 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. If the bug is still relevant, please remove the stalebug whiteboard tag.
No response in a long time. Please reopen if this is still an issue.