Created attachment 87391 [details] Java (javafx + swing) project -> crash X.org server When working with javafx built in swing frame, eclipse freeze (on Parse code) or crash when open WindowBuilder design tab and in many other cases. After the restart writes logs in the attachments. Among other things : 1. X.org segfault: 202.491] (EE) [ 202.491] (EE) Backtrace: [ 202.491] (EE) 0: /usr/bin/X (xorg_backtrace+0x36) [0x7f4a84853516] [ 202.491] (EE) 1: /usr/bin/X (0x7f4a846a3000+0x1b4359) [0x7f4a84857359] [ 202.491] (EE) 2: /lib/x86_64-linux-gnu/libpthread.so.0 (0x7f4a837a6000+0xfbd0) [0x7f4a837b5bd0] [ 202.491] (EE) 3: /usr/lib/x86_64-linux-gnu/libpixman-1.so.0 (pixman_region_intersect+0x24) [0x7f4a83358034] [ 202.491] (EE) 4: /usr/lib/xorg/modules/drivers/intel_drv.so (0x7f4a80f37000+0x5667f) [0x7f4a80f8d67f] [ 202.491] (EE) 5: /usr/bin/X (0x7f4a846a3000+0x132d35) [0x7f4a847d5d35] [ 202.491] (EE) 6: /usr/bin/X (0x7f4a846a3000+0x58af1) [0x7f4a846fbaf1] [ 202.491] (EE) 7: /usr/bin/X (0x7f4a846a3000+0x475aa) [0x7f4a846ea5aa] [ 202.491] (EE) 8: /lib/x86_64-linux-gnu/libc.so.6 (__libc_start_main+0xf5) [0x7f4a823f2ea5] [ 202.491] (EE) 9: /usr/bin/X (0x7f4a846a3000+0x478f1) [0x7f4a846ea8f1] [ 202.491] (EE) [ 202.491] (EE) Segmentation fault at address 0x29 [ 202.491] Fatal server error: [ 202.491] Caught signal 11 (Segmentation fault). Server aborting [ 202.491] [ 202.491] (EE) Please consult the The X.Org Foundation support at http://wiki.x.org for help. 2. X.org close: [ 2944.418] Server terminated successfully (0). Closing log file. This occurs at startup javafx App in attachment.
Already fixed in 2.99.904.
Hm. Please look the logs for Nvidia (in attach). I have Optimus and I checked on both cards. In Nvidia card start javafx+swing app->crash java jvm, but jvm say "crash in out native code".
I am only concerned here about the crash in the DDX, which is indeed fixed. That Java complains about an invalid thread access I have no idea about.
Ok. I try this driver version.
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.