| commit | 3f32f32c87e879ecf9d5bd94fe8fbd1f949f104a | [log] [tgz] |
|---|---|---|
| author | Nikita Nemkin <nikita@nemkin.ru> | Thu Jan 21 13:58:31 2021 +0500 |
| committer | Sravan Kumar Lakkimsetti <sravankumarl@in.ibm.com> | Thu Mar 25 23:40:05 2021 -0400 |
| tree | 3834f82ad938f85e84d46287a59483c88ee99173 | |
| parent | 74cfe5c97ee35d7baa32658ddd19b3e7688a4ce0 [diff] |
Bug 569468 - [GTK3] SWT/GTK3 crash when using GTKLookAndFeel in Swing Swing GTKLookAndFeel relies on the deprecated GDK lock to synchronize GTK function calls from the Event Dispatch Thread. To avoid data races, memory corruption and chrashes when using GTKLookAndFeel, SWT also has to synchronize with the GDK lock. Use GTK event loop functions that perform the necessary locking and unlocking automatically. To allow Swing objects to be created on the main thread, GTK lock has to be reentrant. Since the default lock isn't, replace it with GRecMutex. With GDK locking in place, EventQueue.invokeAndWait called from the main thread is very likely to deadlock and should be avoided. Change-Id: I3b217037f515cb695c1c3ef63387d218b559a617 Signed-off-by: Nikita Nemkin <nikita@nemkin.ru>
Thanks for your interest in this project.
See the following description for how to contribute a feature or a bug fix to SWT.
Information regarding source code management, builds, coding standards, and more and be found under the following link.
Before your contribution can be accepted by the project, you need to create and electronically sign the Eclipse Foundation Contributor License Agreement (CLA).
Contact the project developers via the project's “dev” list.
This project uses Bugzilla to track ongoing development and issues.
Be sure to search for existing bugs before you create another one. Remember that contributions are always welcome!