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

Bug 360527

Summary: workbench is frozen while in design view
Product: z_Archived Reporter: Vlad Gheorghe <vlad.gheorghe>
Component: WindowBuilderAssignee: Alexander Mitin <Alexander.Mitin>
Status: CLOSED FIXED QA Contact:
Severity: major    
Priority: P3 CC: alessio.pollero, clayberg, Konstantin.Scheglov
Version: unspecified   
Target Milestone: ---   
Hardware: PC   
OS: Linux-GTK   
Whiteboard:
Attachments:
Description Flags
jvisualvm thread dump
none
screenshot of non-responsive workbench none

Description Vlad Gheorghe CLA 2011-10-11 06:43:53 EDT
Created attachment 204938 [details]
jvisualvm thread dump

While designing a form with windowbuilder, the workbench gets occasionally frozen.

No user input, mouse or keyboard  is processed by any workbench part (main menu, any view/editor).

However the workbench UI is correctly updated (e.g. on window resize), with the exception of the wb Design>Structure>Properties view.
Comment 1 Vlad Gheorghe CLA 2011-10-11 06:45:24 EDT
Created attachment 204939 [details]
screenshot of non-responsive workbench
Comment 2 Konstantin Scheglov CLA 2011-11-15 13:49:06 EST
It looks that you activated "Quick test/preview window..."
It open new SWT Shell with your Composite and handles all events in this new Shell, so main Eclipse window does not get these events.
To get access to the main Eclipse window, you should close preview Shell first.

If you think that your specific example does not work with test/preview, attach example and reopen bug.
Comment 3 Vlad Gheorghe CLA 2011-11-15 13:58:38 EST
The analysis is correct, except that :
Of course I've "closed" the preview Shell !

That is, I've clicked on the "x" button on the window's frame, and the
preview window disappeared from the display.

However, the workbench could not receive events after this.

I don't understand what more information I could provide as evidence.

Notice that this bug is intermittent.
Comment 4 Alexander Mitin CLA 2011-11-15 14:01:03 EST
Is the threads dump (which you've provided) after the shell closed?
Comment 5 Konstantin Scheglov CLA 2011-11-15 14:01:36 EST
Vlad, you are right.
My colleague Alexander Mitin (who is our Linux expert) already corrected me that I should not close Linux bugs like this.
Comment 6 Vlad Gheorghe CLA 2011-11-15 14:19:36 EST
(In reply to comment #4)
> Is the threads dump (which you've provided) after the shell closed?

Yes.
Comment 7 Alexander Mitin CLA 2011-11-18 08:10:58 EST
Vlad, you actually didn't close that window, you possibly missed the "x" button on the window's frame and got back to the Eclipse main window (by clicking on it) because Test/Preview window is not modal. But since Eclipse is disabled until Test/Preview window is closed, you get non-responsible Eclipse.
I've added a workaround which disposes Test/Preview window on Eclipse window activate.