| commit | 5e26c8581c55815ebb2334588f2cb9910a57b2ba | [log] [tgz] |
|---|---|---|
| author | Alexandr Miloslavskiy <alexandr.miloslavskiy@syntevo.com> | Thu Apr 25 15:19:31 2019 +0200 |
| committer | Alexandr Miloslavskiy <alexandr.miloslavskiy@syntevo.com> | Thu Apr 25 17:05:50 2019 +0200 |
| tree | 75f2c013c85e5149e889ab21f2704ff6841377ec | |
| parent | d90c79a64b1cb6d43c3a9cdcfafd27589651d4f3 [diff] |
Bug 531634 - [GTK] Linux: Handle logoff / shutdown events from session manager Hotfix for first version of the patch. Using System.exit() from Shell's 'SWT.Close' event caused deadlock, because main thread held 'Platform.lock' in its event loop and waited for shutdown hook, which waited for the lock - see also Bug 546743. Since multiple Displays are not possible currently (there's only dead code pretending to support it), it should be OK to have non-static object. Having it non-static removes the need for shutdown hook. Signed-off-by: Alexandr Miloslavskiy <alexandr.miloslavskiy@syntevo.com>
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!