| Re: [eclipse-dev] Crash when using recent versions of SWT on Linux |
|
Hi,
I will open a bug report, but
describes my problem exactly. I will refer to that comment in my bug report.
Thanks,
Will
From: eclipse-dev-bounces@xxxxxxxxxxx <eclipse-dev-bounces@xxxxxxxxxxx> on behalf of Andrey Loskutov <loskutov@xxxxxx>
Sent: 16 November 2020 15:21 To: eclipse-dev@xxxxxxxxxxx <eclipse-dev@xxxxxxxxxxx> Subject: Re: [eclipse-dev] Crash when using recent versions of SWT on Linux Hi Will,
In general most of SWT code expects to be executed on UI (main) thread only, but you seem to work on non UI thread?
If you can provide a standalone reproducer example, please create bug for that, we should discuss on bug.
I guess the new behavior is related to removing locks around native GTK calls.
See
https://bugs.eclipse.org/bugs/show_bug.cgi?id=546743#c17
https://git.eclipse.org/r/c/platform/eclipse.platform.swt/+/155907
https://git.eclipse.org/r/c/platform/eclipse.platform.swt/+/155989 .
Kind regards,
Andrey Loskutov Спасение утопающих - дело рук самих утопающих https://www.eclipse.org/user/aloskutov Gesendet: Donnerstag, 22. Oktober 2020 um 15:46 Uhr
Von: "Rogers, Will (DLSLtd,RAL,LSCI)" <will.rogers@xxxxxxxxxxxxx> An: "eclipse-dev@xxxxxxxxxxx" <eclipse-dev@xxxxxxxxxxx> Betreff: [eclipse-dev] Crash when using recent versions of SWT on Linux
Hi,
I have an Eclipse RCP application that has been around for several years. When updating from Eclipse 2018-12 to 2020-12 I suddenly get a complete crash on Linux (GTK3) when opening a particular editor.
Debugging suggests that I get problems when either creating a new SWT Image object or using a GC to draw on that image when not on the main UI thread. redraw() is always called on the UI thread. I can't recreate this in simple SWT applications.
When doing this I get a variety of problems including 1) complete crashes with the below message and 2) deadlocks, possibly causing my entire Gnome session to lock up.
Has something changed about SWT that causes this problem? Or were we lucky not to see it before?
Thanks in advance,
Will Rogers
---
[xcb] Unknown request in queue while dequeuing [xcb] Most likely this is a multi-threaded client and XInitThreads has not been called [xcb] Aborting, sorry about that. java: xcb_io.c:165: dequeue_pending_request: Assertion `!xcb_xlib_unknown_req_in_deq' failed.
-- This e-mail and any attachments may contain confidential, copyright and or privileged material, and are for the use of the intended addressee only. If you are not the intended addressee or an authorised recipient of the addressee please notify
us of receipt by returning the e-mail and do not use, copy, retain, distribute or disclose the information in or attached to the e-mail.
-- This e-mail and any attachments may contain confidential, copyright and or privileged material, and are for the use of the intended addressee only. If you are not the intended addressee or an authorised recipient of the addressee please notify us of receipt by returning the e-mail and do not use, copy, retain, distribute or disclose the information in or attached to the e-mail. |