Bug 574562

Summary:	possible deadlocks when using Display.wakeup with Display.sleep
Product:	[Eclipse Project] Platform	Reporter:	Jörg Kubitz <jkubitz-eclipse>
Component:	SWT	Assignee:	Platform-SWT-Inbox <platform-swt-inbox>
Status:	NEW ---	QA Contact:
Severity:	normal
Priority:	P3	CC:	Lars.Vogel, nikita
Version:	4.21
Target Milestone:	---
Hardware:	All
OS:	Linux
See Also:	https://bugs.eclipse.org/bugs/show_bug.cgi?id=574556
Whiteboard:

Description Jörg Kubitz

2021-06-30 03:42:59 EDT

Deadlocks have been reported when Display.wakeup() was used together with Display.sleep under linux. See bug 429363, bug 266985, bug 188320. Only Synchronizer.asyncExec(null) was fixed to not use wakeup.

There are still a a dozen calls of wakeup in eclipse which rely on wakeup to work - which it does not under GTK.

I ask to either 
a) deprecate wakeup and let clients use Synchronizer.asyncExec(null) instead or
b) port the fix of Synchronizer.asyncExec(null) into Display.wakeup

I am not using linux so i cannot reproduce it => i wont fix it myself.

Comment 1 Lars Vogel

2021-07-01 08:29:25 EDT

Nikita, WDYT?