Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 359960 - Eclipse deadlocks completely while saving after adding a data-binding from a widget to a model object
Summary: Eclipse deadlocks completely while saving after adding a data-binding from a ...
Status: CLOSED WORKSFORME
Alias: None
Product: z_Archived
Classification: Eclipse Foundation
Component: WindowBuilder (show other bugs)
Version: unspecified   Edit
Hardware: PC Linux
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Project Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-10-05 07:00 EDT by Jesper Eskilson CLA
Modified: 2021-06-04 16:45 EDT (History)
1 user (show)

See Also:


Attachments
Thread dump at the time of the deadlock. (33.13 KB, text/plain)
2011-10-05 07:01 EDT, Jesper Eskilson CLA
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description Jesper Eskilson CLA 2011-10-05 07:00:37 EDT
Build Identifier: M20110909-1335

Eclipse deadlocks completely while saving the source file after I've added a data-binding from a checkbox to a member in a model object. Taking a thread dump using JVisualVM shows the main thread being stuck here:

"main" prio=10 tid=0x0000000001f6f800 nid=0x7208 runnable [0x00007f98c925c000]
   java.lang.Thread.State: RUNNABLE
	at java.lang.Throwable.getStackTraceElement(Native Method)
	at java.lang.Throwable.getOurStackTrace(Throwable.java:608)
	- locked <0x00000000ec578f98> (a java.lang.Exception)
	at java.lang.Throwable.getStackTrace(Throwable.java:599)
	at org.eclipse.wb.internal.core.editor.UndoManager$6.isStillInSave(UndoManager.java:341)
	at org.eclipse.wb.internal.core.editor.UndoManager$6.run(UndoManager.java:325)
	at org.eclipse.swt.widgets.Display.timerProc(Display.java:4154)
	at org.eclipse.swt.internal.gtk.OS._g_main_context_iteration(Native Method)
	at org.eclipse.swt.internal.gtk.OS.g_main_context_iteration(OS.java:2276)
	at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3207)
	at org.eclipse.jface.operation.ModalContext$ModalContextThread.block(ModalContext.java:173)
	at org.eclipse.jface.operation.ModalContext.run(ModalContext.java:388)
	at org.eclipse.jface.window.ApplicationWindow$1.run(ApplicationWindow.java:759)
	at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:70)

Unchecking the preference setting "Format source code (and reparse) on editor save" prevents the deadlock.


Reproducible: Always

Steps to Reproduce:
1. Select "format source code (and reparse) on editor save"
2. Add a data-binding between a widget and a model object. (I haven't tried different widgets or model objects, but since the problem disappears with changing the preferences as described above, I guess that won't matter.)
3. Save the file. (Not completely sure if this step is necessary.
Comment 1 Jesper Eskilson CLA 2011-10-05 07:01:59 EDT
Created attachment 204583 [details]
Thread dump at the time of the deadlock.
Comment 2 Eric Clayberg CLA 2011-10-08 12:54:30 EDT
We were unable to reproduce this. 

Please provide a complete test case and re-open this case. Also include your complete Eclipse ".log" file and Eclipse configuration details.