Hmm.., i found the source of the crash. Interesting finding. My linux box was affected by the bug (!xcb_xlib_threads_sequence_lost), i have fixed that in Libx11 with the proposed fix. Google-chrome, pcfman, geany, meld and some other application i can't remember was affected by this bug. i haad bumped the libx11 version to 1.6.4-3ubuntu0.3. It was all fine, some time later Google-chrome released version 85.0.4183.83, so the crashes started with this version and Chromium 84.0.4147.105 was not affected. Google-chrome 84.0.4147.105 was not affected also.
Recently i updated the Ubuntu and a new security fix in libx11 was installed: libx11 (2:1.6.4-3ubuntu0.3) bionic-security; urgency=medium , which has overwritten my own 1.6.4-3ubuntu0.3 with the "!xcb_xlib_threads_sequence_lost" fix. After this update i started to having the "!xcb_xlib_threads_sequence_lost" issue again, went back to libx11, bumped the version and applied the "!xcb_xlib_threads_sequence_lost" fix. Now Google-chrome and Chromium crash with SIGSEGV when an input is in the window. So, 85.0.4183.83 engine has changed the way it handles input (could be to mitigate the !xcb_xlib_threads_sequence_lost issue ???). The odd thing is FireFox is not affected. Can someone point me to what have changed from 84.0.4147.105 to 85.0.4183.83? My linux box is unstable with !xcb_xlib_threads_sequence_lost issue, fixing that makes 85.0.4183.83 crash. ** Summary changed: - Google Chrome 85.0.4183.83 crahses with SIGSEGV + Chromium-browser and Google Chrome 85.0.4183.83 crashes with SIGSEGV -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1893484 Title: Chromium-browser and Google Chrome 85.0.4183.83 crashes with SIGSEGV To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1893484/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
