When using qutebrowser 1.13.1 with the QT5 WebEngine backend, the render process for WebEngine crashes when loading certain webpages. Example of such a page https://qutebrowser.org/ the core dump created from this is as follows: (lldb) target create --core "QtWebEngineProcess.core" Core file '/usr/home/vendion/QtWebEngineProcess.core' (x86_64) was loaded. (lldb) thread backtrace all * thread #1, name = 'QtWebEngineProcess', stop reason = signal SIGTRAP * frame #0: 0x0000000808095777 frame #1: 0x00007fffffff2bc0 thread #2, name = 'QtWebEngineProcess', stop reason = signal SIGTRAP frame #0: 0x0000000817bf517a frame #1: 0x00000008007297e3 thread #3, name = 'QtWebEngineProcess', stop reason = signal SIGTRAP frame #0: 0x0000000800734edc frame #1: 0x00000008007286c0 thread #4, name = 'QtWebEngineProcess', stop reason = signal SIGTRAP frame #0: 0x0000000817bf517a frame #1: 0x00000008007297e3 thread #5, name = 'QtWebEngineProcess', stop reason = signal SIGTRAP frame #0: 0x0000000800734edc frame #1: 0x00000008007286c0 thread #6, name = 'QtWebEngineProcess', stop reason = signal SIGTRAP frame #0: 0x0000000800734edc frame #1: 0x00000008007286c0 thread #7, name = 'QtWebEngineProcess', stop reason = signal SIGTRAP frame #0: 0x0000000800734edc frame #1: 0x00000008007286c0 thread #8, name = 'QtWebEngineProcess', stop reason = signal SIGTRAP frame #0: 0x0000000800734edc frame #1: 0x00000008007286c0 thread #9, name = 'QtWebEngineProcess', stop reason = signal SIGTRAP frame #0: 0x0000000800734edc frame #1: 0x00000008007286c0 thread #10, name = 'QtWebEngineProcess', stop reason = signal SIGTRAP frame #0: 0x0000000800734edc frame #1: 0x00000008007286c0 thread #11, name = 'QtWebEngineProcess', stop reason = signal SIGTRAP frame #0: 0x0000000800734edc frame #1: 0x00000008007286c0 thread #12, name = 'QtWebEngineProcess', stop reason = signal SIGTRAP frame #0: 0x0000000800734edc frame #1: 0x00000008007286c0 thread #13, name = 'QtWebEngineProcess', stop reason = signal SIGTRAP frame #0: 0x0000000800734edc frame #1: 0x00000008007286c0 Interestingly I can open the same page using a different browser (Konqueror) also using QT WebEngine and the page loads correctly which seems to point to a issue between Qutebrowser and WebEngine.
(In reply to Adam Jimerson from comment #0) Hi Adam, We'll probably need help from upstream to understand this, could you please create an issue here: https://github.com/qutebrowser/qutebrowser/issues? Also, does this imply that things were working fine with 1.13.0? Thanks
Sorry for the late reply, I missed your comment. I went ahead and opened a ticket upstream at https://github.com/qutebrowser/qutebrowser/issues/5773
(In reply to Roman Bogorodskiy from comment #1) > Also, does this imply that things were working fine with 1.13.0? Yes everything was working fine with 1.13.0, it wasn't until the 1.13.1 update (or an update to QtWebEngine that this started happening.
(In reply to Adam Jimerson from comment #2) Thanks; subscribed.
Following the recommendation posted by the upstream author here https://github.com/qutebrowser/qutebrowser/issues/5773#issuecomment-704944886 this is a bug in QT/QtWebEngine 5.15.0. As such I commented out that setting in my config and it seems to be working so far. It appears an this is fixed it QT 5.15.1, as such it is probably safe to close this issue.