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

Bug 351295

Summary: Fast refreshing editor --> frozen eclipse.
Product: z_Archived Reporter: marcin.miedzinski
Component: WindowBuilderAssignee: Project Inbox <wb.xwt-inbox>
Status: CLOSED WORKSFORME QA Contact:
Severity: normal    
Priority: P3 CC: Alexander.Mitin, Konstantin.Scheglov, michal.stolarski
Version: unspecified   
Target Milestone: ---   
Hardware: PC   
OS: Linux   
Whiteboard:
Attachments:
Description Flags
Eclipse thread dump. none

Description marcin.miedzinski CLA 2011-07-06 05:40:58 EDT 
Build Identifier: 20110218-0911

Fast pressing F5 in XWTDesigner cause eclipse crash.

Reproducible: Sometimes

Steps to Reproduce:
1. Create new XWT application
2. Add 2-3 components to form
3. Press several times F5 key.
Comment 1 Konstantin Scheglov CLA 2011-07-07 11:01:29 EDT 
Can not reproduce.
Do you have JVM crash logs (files  hs_err_pid*.log)?
Comment 2 marcin.miedzinski CLA 2011-07-08 03:03:45 EDT 
(In reply to comment #1)
> Can not reproduce.
> Do you have JVM crash logs (files  hs_err_pid*.log)?

Unfortunately eclipse doesn't show stack, in *.log file also don't any information about this error.
I downloaded source of WB, and run an eclipse aplication, when I try a several times refreshing a form, editor become frozen. I must terminate editor from primary eclipse, but there aren't any massage.
Comment 3 Konstantin Scheglov CLA 2011-07-08 09:30:10 EDT 
Create thread stack trace.
For example on Windows run Eclipse as:
eclipsec -clean -data workspace -vmargs -XX:MaxPermSize=192m -Xms1024m -Xmx1024m > threads.log

and when it become frozen, press Ctrl+Break (IIRC kill -1 in Linux).
Then attach this log file.
Comment 4 marcin.miedzinski CLA 2011-07-11 04:03:00 EDT 
(In reply to comment #3)
> Create thread stack trace.
> For example on Windows run Eclipse as:
> eclipsec -clean -data workspace -vmargs -XX:MaxPermSize=192m -Xms1024m
> -Xmx1024m > threads.log
> 
> and when it become frozen, press Ctrl+Break (IIRC kill -1 in Linux).
> Then attach this log file.

Log file is empty. I suspect that, the problem may not occurs on every operating systems. I'm using Ubuntu x64 
(Linux PC31 2.6.35-28-generic #50-Ubuntu SMP Fri Mar 18 18:42:20 UTC 2011 x86_64 GNU/Linux).
Comment 5 Alexander Mitin CLA 2011-07-11 08:59:13 EDT 
For Linux, run Eclipse from the console and when it hangs execute 'kill -3 <eclipse_pid>' command, you'll get the Java threads dump.
Comment 6 Michal CLA 2011-07-14 02:53:43 EDT 
Created attachment 199634 [details]
Eclipse thread dump.

Hi, I'm attaching thread dump. I ran eclipse with command:
eclipse -clean -data ~/temp/workspace -vmargs -XX:MaxPermSize=192m -Xms1024m -Xmx1024m > threads.log

After designer have stalled I sent SIGQUIT (3) to eclipse process. 

NOTE: Eclipse does not crash, main menu and most of other functionality works. Only designer editor hangs. (and probably some other features, e.g. I can not open "Error Log" view).
Comment 7 Alexander Mitin CLA 2011-07-14 06:40:57 EDT 
@Michal, 
Try to activate 'Disable preview window flickering workarounds' option in WindowBuilder preferences.
Comment 8 Michal CLA 2011-07-14 07:22:15 EDT 
Hi Alexander,

it solved problem for me, thanks!

Cheers,
Mike
Comment 9 marcin.miedzinski CLA 2011-07-14 07:31:23 EDT 
Problem solved. Thanks.
Comment 10 Alexander Mitin CLA 2011-07-18 14:37:49 EDT 
Closed.