| Summary: | [Cocoa] DND drag to table after previous drag threw exception causes SWT native code to hang | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Eclipse Project] Platform | Reporter: | Ed Gow <elg> | ||||
| Component: | SWT | Assignee: | Lakshmi P Shanmugam <lshanmug> | ||||
| Status: | CLOSED DUPLICATE | QA Contact: | Silenio Quarti <Silenio_Quarti> | ||||
| Severity: | critical | ||||||
| Priority: | P3 | CC: | eclipse.felipe, lshanmug, ned.twigg, remy.suen, Silenio_Quarti | ||||
| Version: | 3.7 | ||||||
| Target Milestone: | --- | ||||||
| Hardware: | Macintosh | ||||||
| OS: | Mac OS X | ||||||
| Whiteboard: | |||||||
| Attachments: |
|
||||||
|
Description
Ed Gow
Created attachment 200946 [details]
Code to reproduce.
Same problem occurs in Eclipse 3.7 and 3.6.1.
Similar, perhaps even same, problem occurs intermittently on first drag, but I cannot provide a test case to reproduce it. when an exception happens in an event handler it has to handled *before* the event handler returns. Otherwise SWT will stop receving call ins. Basically, if you have a expection in your code, you need to fix it. is that the case ? (In reply to comment #3) > when an exception happens in an event handler it has to handled *before* the > event handler returns. Otherwise SWT will stop receving call ins. > > Basically, if you have a expection in your code, you need to fix it. > is that the case ? It would be nice, though, if the UI did not lock up and consume all available system memory. The Windows version does not do that, and it upsets the Mac users when it happens. Also, the same symptoms happen occasionally during a drop w/o an exception. I cannot reproduce that reliably, so I submitted this test case in the hopes that fixing this one might fix both. I'm seeing this exact same stacktrace in the latest SWT (4.8.0). No exception in my case, just clicking a table intermittently causes a hang. *** This bug has been marked as a duplicate of bug 395381 *** |