Hey again,
On Mon, Sep 21, 2020 at 12:17:57PM -0300, felipe wrote:
> Hey,
>
> > For 1), do you see those QtWebEngineProcess crashes when you run
> > "coredumpctl list"? If so, can you please show "coredumpctl info PID"
> > with the PID from the list? If not, can you check whether you can
> > reproduce them (making the entire browser crash) when you run with
> > "--qt-flag single-process"?
>
> I have attached coredumpctl info when it crashes using --temp-basedir.
>
> Running with:
> $ qutebrowser --qt-flag single-process
> [1] 5850 illegal hardware instruction (core dumped) qutebrowser
> --qt-flag single-process
> The browser starts with a blank page and when I try to open any webpage, it
> crashes.
>
> I have also attached coredumpctl of this crash.
>
>
> > For 2), it looks like there's no libqt5webengine5-dbg{,sym} package in
> > the debian archives. Could you check if you find them if you run e.g.
> > find-dbgsym-packages on /usr/lib/x86_64-linux-gnu/libQt5WebEngine.so.5.14.2
> > https://wiki.debian.org/HowToGetABacktrace#Installing_the_debugging_symbols
>
> After adding deb 'http://deb.debian.org/debian-debug/ unstable-debug
> main' to my '/etc/apt/sources.list' and installing
> 'libfile-slurper-perl' and 'libfile-which-perl', I find some debug
> symbols available:
>
> $ find-dbgsym-packages
> /usr/lib/x86_64-linux-gnu/libQt5WebEngine.so.5.14.2
>
> I have attached the file 'find-dbgsym-packages.txt'You will need at lesat libqt5webengine5-dbgsym and perhaps libqt5webenginecore5-dbgsym as well. From what I see in the attached coredumpctl outputs, those happened before you installed the symbols, right? Can you try again, so that you'd hopefully get a stacktrace which says more than just "n/a" for the entries? :) > > If getting more info via coredumpctl didn't work, but you can reproduce > > with --qt-flag single-process, can you please do something like: > > > > gdb -ex r --args /usr/bin/python3 -m qutebrowser --temp-basedir > > --qt-flag single-process > > $ sudo gdb -ex r --args /usr/bin/python3 -m qutebrowser --temp-basedir > --qt-flag single-process Please don't run with 'sudo'. This can cause various other issues (since Chromium's sandboxing doesn't work properly as root) and running a browser as root is a bad idea in general ;) > [...] > > <RET> > Thread 40 "Chrome_InProcRe" received signal SIGILL, Illegal instruction. > [Switching to Thread 0x7fff58a89700 (LWP 12375)] > 0x00007fffea1b128f in > blink::CompositedLayerMapping::ComputeBoundsOfOwningLayer(blink::PaintLayer > const*, > blink::IntRect&, blink::IntRect&, blink::PhysicalOffset&, blink::IntPoint&) > () from > /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 > > (gdb) bt > #0 0x00007fffea1b128f in > blink::CompositedLayerMapping::ComputeBoundsOfOwningLayer(blink::PaintLayer > const*, > blink::IntRect&, blink::IntRect&, blink::PhysicalOffset&, blink::IntPoint&) > () at > /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 > #1 0x00007fffea1bc054 in > blink::CompositedLayerMapping::UpdateGraphicsLayerGeometry(blink::PaintLayer > const*, > blink::PaintLayep Looks like your output/mail was cut off here, so it's difficult to say what's happening exactly - but from what I can tell so far, this most like is indeed an issue in QtWebEngine and not qutebrowser. Can you check if you get the same crashes with another QtWebEngine-based browser such as falkon? If so, this report should probably be moved to libqt5webengine5, though having the full stack traces would still be useful for the maintainers of that package :) Thanks, Florian -- m...@the-compiler.org (Mail/XMPP) | https://www.qutebrowser.org https://bruhin.software/ | https://github.com/sponsors/The-Compiler/ GPG: 916E B0C8 FD55 A072 | https://the-compiler.org/pubkey.asc I love long mails! | https://email.is-not-s.ms/
signature.asc
Description: PGP signature
