You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
TL;DR: Deadlock on Linux GTK when calling SikuliX1 API functions from SWT application context: either main or separate thread. Screen and SWT Display seem to hate each other. 馃榾
Long story short, I am trying to use SikuliX1 from a SWT GUI thread, either directly, or via syncExec (starting a different thread), and I am running into a deadlock between the SWT event loop, and SikuliX1 features (mostly screen.selectRegion for now, but expecting more problems). It seems to get stuck somewhere in the OverlayCapture, or in the AWT getRGBPixelsImpl native method.
Question is, can I make SikuliX1 and the SWT event loop play nice with each other?
The text was updated successfully, but these errors were encountered:
TL;DR: Deadlock on Linux GTK when calling SikuliX1 API functions from SWT application context: either main or separate thread. Screen and SWT Display seem to hate each other. 馃榾
Long story short, I am trying to use SikuliX1 from a SWT GUI thread, either directly, or via syncExec (starting a different thread), and I am running into a deadlock between the SWT event loop, and SikuliX1 features (mostly screen.selectRegion for now, but expecting more problems). It seems to get stuck somewhere in the OverlayCapture, or in the AWT getRGBPixelsImpl native method.
Question is, can I make SikuliX1 and the SWT event loop play nice with each other?
The text was updated successfully, but these errors were encountered: