Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 325607

Summary: Eclipse crashed - once again
Product: [Eclipse Project] Platform Reporter: Johannes Rieken <johannes_rieken>
Component: SWTAssignee: Scott Kovatch <skovatch>
Status: RESOLVED FIXED QA Contact: Silenio Quarti <Silenio_Quarti>
Severity: major    
Priority: P3 CC: eclipse.user, njbartlett, skovatch
Version: 4.0   
Target Milestone: 3.7 M3   
Hardware: Macintosh   
OS: Mac OS X   
Whiteboard:
Attachments:
Description Flags
dump file none

Description Johannes Rieken CLA 2010-09-17 11:06:58 EDT 
Build Identifier: 3.6

I've lost count how many time I have filed a bug like this, and I don't even know if my eclipse crashes always because of the same reason. I know that this is starting to get on my nerves. I see that this is related to Safari and might not be fixable by the swt team. In that case I wonder if there a switch that lets me use FF/gecko instead.

Reproducible: Sometimes
Comment 1 Johannes Rieken CLA 2010-09-17 11:07:40 EDT 
Created attachment 179124 [details]
dump file
Comment 2 Scott Kovatch CLA 2010-09-17 11:39:30 EDT 
The stack trace makes me think we're sending an event to a disposed view. A mouse move/scroll wheel makes the popup code hint disappear, but we aren't finished sending the event up to AppKit for the default behavior, so the message gets to a disposed control.

I think we can guard against that, but it's so difficult to reproduce that it would only be a speculative change at this point.
Comment 3 Scott Kovatch CLA 2010-09-17 18:18:07 EDT 
Fixed (I think) > 20100917. Please grab an I-build next week and see if it still reproduces for you.
Comment 4 Johannes Rieken CLA 2010-09-20 04:12:39 EDT 
Thanks for addressing this so quickly. I'll keep you updated once I've updated my install.
Comment 5 Scott Kovatch CLA 2010-09-28 12:36:02 EDT 
*** Bug 303904 has been marked as a duplicate of this bug. ***
Comment 6 Scott Kovatch CLA 2011-01-02 16:10:35 EST 
*** Bug 333388 has been marked as a duplicate of this bug. ***