Bug 574562 - possible deadlocks when using Display.wakeup with Display.sleep
Summary: possible deadlocks when using Display.wakeup with Display.sleep
Status: NEW
Alias: None
Product: Platform
Classification: Eclipse Project
Component: SWT (show other bugs)
Version: 4.21   Edit
Hardware: All Linux
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Platform-SWT-Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2021-06-30 03:42 EDT by Jörg Kubitz CLA
Modified: 2021-07-01 08:29 EDT (History)
2 users (show)

See Also:

Attachments
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 Jörg Kubitz CLA 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 CLA 2021-07-01 08:29:25 EDT 
Nikita, WDYT?