Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 346099 - Window Builder Freezing
Summary: Window Builder Freezing
Status: CLOSED WORKSFORME
Alias: None
Product: z_Archived
Classification: Eclipse Foundation
Component: WindowBuilder (show other bugs)
Version: unspecified   Edit
Hardware: PC Windows 7
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Project inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-05-17 10:22 EDT by khusta_2000 CLA
Modified: 2021-06-04 16:45 EDT (History)
3 users (show)

See Also:

Attachments
Eclipse dump from startup... (15.47 KB, text/plain)
2011-05-17 11:38 EDT, khusta_2000 CLA 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description khusta_2000 CLA 2011-05-17 10:22:15 EDT 
Build Identifier: 20110301-1815

I am working on a swing project with about 10 JPanels and 4 JDialogs and out of nowhere when I switch from code view to design view Eclipse hangs.

My code has no errors or anything...

Reproducible: Always

Steps to Reproduce:
1.When I try to switch to design view of WindowBuilder
2.
3.
Comment 1 Jay Arthanareeswaran CLA 2011-05-17 10:26:21 EDT 
While it's hung, can you please get a heap dump?
Comment 2 Olivier Thomann CLA 2011-05-17 10:26:54 EDT 
Move to VE
Comment 3 khusta_2000 CLA 2011-05-17 10:56:57 EDT 
(In reply to comment #1)
> While it's hung, can you please get a heap dump?

Hi,


Could you please guide me on how to get that?


Thanks.
Comment 4 khusta_2000 CLA 2011-05-17 10:58:21 EDT 
(In reply to comment #2)
> Move to VE

I would if I could but I am in the middle of a project and I am using JGoodies forms which  - the last time I checked - VE didn't support.



Thanks
Comment 5 khusta_2000 CLA 2011-05-17 11:04:51 EDT 
(In reply to comment #2)
> Move to VE

I would if I could but I am in the middle of a project and I am using JGoodies forms which  - the last time I checked - VE didn't support.



Thanks
Comment 6 Olivier Thomann CLA 2011-05-17 11:07:10 EDT 
Sorry the pb should be reported against Window Builder and not VE.
Comment 7 Olivier Thomann CLA 2011-05-17 11:07:56 EDT 
> Could you please guide me on how to get that?
Please check:
http://wiki.eclipse.org/index.php/How_to_report_a_deadlock#Getting_a_stack_trace_on_Windows
Comment 8 khusta_2000 CLA 2011-05-17 11:38:00 EDT 
Created attachment 195880 [details]
Eclipse dump from startup...

Please see attached what I get from the dump...
Comment 9 khusta_2000 CLA 2011-05-17 11:38:42 EDT 
I have not made and attached the dump as requested...


Thanking you again.
Comment 10 khusta_2000 CLA 2011-05-17 11:40:32 EDT 
(In reply to comment #9)
> I have made and attached the dump as requested...
> 
> 
> Thanking you again.

*** This bug has been marked as a duplicate of bug 8 ***
Comment 11 khusta_2000 CLA 2011-05-17 11:51:25 EDT 
(In reply to comment #10)
> (In reply to comment #9)
> > I have made and attached the dump as requested...
> > 
> > 
> > Thanking you again.
> 
> *** This bug has been marked as a duplicate of bug 8 ***
Comment 12 khusta_2000 CLA 2011-05-17 11:54:02 EDT 
(In reply to comment #10)
> (In reply to comment #9)
> > I have made and attached the dump as requested...
> > 
> > 
> > Thanking you again.
>
Comment 13 khusta_2000 CLA 2011-05-17 11:54:18 EDT 
(In reply to comment #11)
> (In reply to comment #10)
> > (In reply to comment #9)
> > > I have made and attached the dump as requested...
Comment 14 Eric Clayberg CLA 2011-05-17 14:23:29 EDT 
We are unable to reproduce any problem based on the information you have provided so far, and nothing in the log you provided indicates a problem with WindowBuider. 

Please provide a complete test case (that will reproduce the problem) and reopen this case. We also need to see a heap dump when Eclipse hangs as suggested earlier (what you attached is just the startup log and does not provide any insight).

BTW, the most common cause for something like this a bug in a custom component that you are using. Check carefully that you are not relying or waiting on some runtime state that does not apply.