Summary: | Possible Deadlock in JFace ModalContext | ||||||
---|---|---|---|---|---|---|---|
Product: | [Eclipse Project] Platform | Reporter: | Tobias Vogele <register> | ||||
Component: | SWT | Assignee: | Silenio Quarti <Silenio_Quarti> | ||||
Status: | RESOLVED FIXED | QA Contact: | |||||
Severity: | normal | ||||||
Priority: | P3 | CC: | fengyaoy, gheorghe, krzysztof.daniel, natalia.bartol, Silenio_Quarti, steve_northover | ||||
Version: | 3.2.2 | ||||||
Target Milestone: | 3.5 M7 | ||||||
Hardware: | PC | ||||||
OS: | Linux-GTK | ||||||
Whiteboard: | |||||||
Attachments: |
|
Description
Tobias Vogele
2007-05-22 10:17:23 EDT
This one is ours. Consider for 3.3 RC2. Created attachment 68179 [details]
Patch for problem.
It seems that the bug is still alive. I have an application that worked well until end of last year. Then there was a hardware failure. The new hardware is dual core and runs under a 64 bit Linux, with Eclipse 3.3.1.1 (compared to single core and 32 bit Linux before). The application uses ModalContext quite often. On the new hardware the application sometimes seems to hang. As soon as I move the mouse the application continues. The same application still runs without problems on a single core 32 bit Windows machine (Eclipse 3.3.1.1). I've played around a little bit and tested something like try { ModalContext.run(new IRunnableWithProgress() { public void run(IProgressMonitor monitor) throws InvocationTargetException, InterruptedException { System.out.println("Start"); // Do something here... System.out.println("Stop"); throw new InterruptedException("Dummy"); } }, true, new NullProgressMonitor(), SWTBase.getDisplay()); } catch (Exception e) { e.printStackTrace(); } If the "hang" occurs, the real work is already done, the "Stop" was printed, but the Exception is not thrown. As all the real work completes successfully. it seems to me that something goes wrong in the ModalContext.run() method. I'm assuming that it must have to do something with the dual core hardware. Silenio, please put the patch in or use the same solution that we used for the same problem on Mac Leopard. I still see this problem in SWT-GTK 3.4. https://bugs.eclipse.org/bugs/show_bug.cgi?id=266985 Let's fix this for 3.5 M7. Fixed in HEAD > 20090413 |