Bug#970478: ERROR: Renderer process crashed when using qtwebengine backend.
Hi! > As we now have Qt WebEngine 5.15.2 in testing and sid, can we mark this > bug as fixed? As suggested before, I avoided qtwebengine version 5.15.1 first by downgrading to 5.15.0 and then upgrading to 5.15.2 when it did become available. It worked without incidents on my 2 machines, so it was fixed for me.
Bug#970478: ERROR: Renderer process crashed when using qtwebengine backend.
Hi Florian, On Tue, Sep 22, 2020 at 03:04:28PM +0200, Florian Bruhin wrote: > Let me note that QtWebEngine 5.15.1 has another bug causing frequent > renderer process crashes: https://bugreports.qt.io/browse/QTBUG-86752 > > I'm currently trying to bisect it because it seems to work in the > current 5.15 branch - but I suppose it might be the Chromium update > between 5.15.1 and 5.15(.2) fixing this again. > > Thus, I'd recommend either staying with 5.15.0, or using the current > 5.15 HEAD (or waiting for 5.15.2). That's bad news :( Qt 5.15 is requested by too many people, and I really don't want to wait until 5.15.2 because that may be a quite close to our transition freeze (2021-01-12). But if we land 5.15.1 now (in a few weeks), then it will be easier and faster to update to 5.15.2 whenever it gets released, if it is before the transition freeze. In any case, I have subscribed to upstream bug and keeping an eye on it — if a concrete patch is identified then I will cherry-pick it to our 5.15 packaging. -- Dmitry Shachnev signature.asc Description: PGP signature
Bug#970478: ERROR: Renderer process crashed when using qtwebengine backend.
Hi Dmitry, On Tue, Sep 22, 2020 at 03:56:15PM +0300, Dmitry Shachnev wrote: > Hi Florian! > > On Tue, Sep 22, 2020 at 01:48:17PM +0200, Florian Bruhin wrote: > > reassign -1 libqt5webenginecore5 5.14.2+dfsg1-5 > > thanks > > > > Hey, > > > > Since you can reproduce this with Falkon, it definitely isn't an issue > > in qutebrowser. Reassigning this to QtWebEngine. Let's hope it works, > > I'm not too experienced with using Debian's BTS - whoever is on the > > receiving end, please let me know if I messed up something :) > > I see you ended up sending a mail to cont...@bugs.debian.org. Another way is > sending a mail to the bug itself but prefixing the commands with "Control: ". Ah, thanks! I guess with that, the "-1" would've worked properly as well. I ended up getting an error and trying again with explicitly specifying the bug number. > > Thanks! For reference, here's a demangled version of the relevant stack > > trace: > > > > #0 0x7f6842b6928f > > blink::CompositedLayerMapping::ComputeBoundsOfOwningLayer(blink::PaintLayer > > const*, blink::IntRect&, blink::IntRect&, blink::PhysicalOffset&, > > blink::IntPoint&) (libQt5WebEngineCore.so.5 0x462928f) > > #1 0x7f6842b74054 > > blink::CompositedLayerMapping::UpdateGraphicsLayerGeometry(blink::PaintLayer > > const*, blink::PaintLayer const*, WTF::Vector > WTF::PartitionAllocator>&, blink::GraphicsLayerUpdater::UpdateContext&) > > (libQt5WebEngineCore.so.5 0x4634054) > > #2 0x7f6842b76561 > > blink::GraphicsLayerUpdater::UpdateRecursive(blink::PaintLayer&, > > blink::GraphicsLayerUpdater::UpdateType, > > blink::GraphicsLayerUpdater::UpdateContext&, > > WTF::Vector&) > > (libQt5WebEngineCore.so.5 0x4636561) > > #3 0x7f6842b764ca > > blink::GraphicsLayerUpdater::UpdateRecursive(blink::PaintLayer&, > > blink::GraphicsLayerUpdater::UpdateType, > > blink::GraphicsLayerUpdater::UpdateContext&, > > WTF::Vector&) > > (libQt5WebEngineCore.so.5 0x46364ca) > > #4 0x7f6842b764ca > > blink::GraphicsLayerUpdater::UpdateRecursive(blink::PaintLayer&, > > blink::GraphicsLayerUpdater::UpdateType, > > blink::GraphicsLayerUpdater::UpdateContext&, > > WTF::Vector&) > > (libQt5WebEngineCore.so.5 0x46364ca) > > #5 0x7f6842b764ca > > blink::GraphicsLayerUpdater::UpdateRecursive(blink::PaintLayer&, > > blink::GraphicsLayerUpdater::UpdateType, > > blink::GraphicsLayerUpdater::UpdateContext&, > > WTF::Vector&) > > (libQt5WebEngineCore.so.5 0x46364ca) > > [...] > > > > From a quick search in QtWebEngine's and Chromium's bugtracker I > > couldn't find anything relevant... I also don't remember seeing this > > stacktrace before. > > I also have no clue about this. Unfortunately we build Qt WebEngine without > any debugging information so it is impossible to get the line numbers. > But I see the ComputeBoundsOfOwningLayer method changed between Qt 5.14 and > 5.15, so let's see if upgrading to Qt 5.15 helps here (I am working on it). Let me note that QtWebEngine 5.15.1 has another bug causing frequent renderer process crashes: https://bugreports.qt.io/browse/QTBUG-86752 I'm currently trying to bisect it because it seems to work in the current 5.15 branch - but I suppose it might be the Chromium update between 5.15.1 and 5.15(.2) fixing this again. Thus, I'd recommend either staying with 5.15.0, or using the current 5.15 HEAD (or waiting for 5.15.2). 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
Bug#970478: ERROR: Renderer process crashed when using qtwebengine backend.
Hi Florian! On Tue, Sep 22, 2020 at 01:48:17PM +0200, Florian Bruhin wrote: > reassign -1 libqt5webenginecore5 5.14.2+dfsg1-5 > thanks > > Hey, > > Since you can reproduce this with Falkon, it definitely isn't an issue > in qutebrowser. Reassigning this to QtWebEngine. Let's hope it works, > I'm not too experienced with using Debian's BTS - whoever is on the > receiving end, please let me know if I messed up something :) I see you ended up sending a mail to cont...@bugs.debian.org. Another way is sending a mail to the bug itself but prefixing the commands with "Control: ". > Thanks! For reference, here's a demangled version of the relevant stack > trace: > > #0 0x7f6842b6928f > blink::CompositedLayerMapping::ComputeBoundsOfOwningLayer(blink::PaintLayer > const*, blink::IntRect&, blink::IntRect&, blink::PhysicalOffset&, > blink::IntPoint&) (libQt5WebEngineCore.so.5 0x462928f) > #1 0x7f6842b74054 > blink::CompositedLayerMapping::UpdateGraphicsLayerGeometry(blink::PaintLayer > const*, blink::PaintLayer const*, WTF::Vector WTF::PartitionAllocator>&, blink::GraphicsLayerUpdater::UpdateContext&) > (libQt5WebEngineCore.so.5 0x4634054) > #2 0x7f6842b76561 > blink::GraphicsLayerUpdater::UpdateRecursive(blink::PaintLayer&, > blink::GraphicsLayerUpdater::UpdateType, > blink::GraphicsLayerUpdater::UpdateContext&, WTF::Vector 0u, WTF::PartitionAllocator>&) (libQt5WebEngineCore.so.5 0x4636561) > #3 0x7f6842b764ca > blink::GraphicsLayerUpdater::UpdateRecursive(blink::PaintLayer&, > blink::GraphicsLayerUpdater::UpdateType, > blink::GraphicsLayerUpdater::UpdateContext&, WTF::Vector 0u, WTF::PartitionAllocator>&) (libQt5WebEngineCore.so.5 0x46364ca) > #4 0x7f6842b764ca > blink::GraphicsLayerUpdater::UpdateRecursive(blink::PaintLayer&, > blink::GraphicsLayerUpdater::UpdateType, > blink::GraphicsLayerUpdater::UpdateContext&, WTF::Vector 0u, WTF::PartitionAllocator>&) (libQt5WebEngineCore.so.5 0x46364ca) > #5 0x7f6842b764ca > blink::GraphicsLayerUpdater::UpdateRecursive(blink::PaintLayer&, > blink::GraphicsLayerUpdater::UpdateType, > blink::GraphicsLayerUpdater::UpdateContext&, WTF::Vector 0u, WTF::PartitionAllocator>&) (libQt5WebEngineCore.so.5 0x46364ca) > [...] > > From a quick search in QtWebEngine's and Chromium's bugtracker I > couldn't find anything relevant... I also don't remember seeing this > stacktrace before. I also have no clue about this. Unfortunately we build Qt WebEngine without any debugging information so it is impossible to get the line numbers. But I see the ComputeBoundsOfOwningLayer method changed between Qt 5.14 and 5.15, so let's see if upgrading to Qt 5.15 helps here (I am working on it). -- Dmitry Shachnev signature.asc Description: PGP signature
Bug#970478: ERROR: Renderer process crashed when using qtwebengine backend.
reassign -1 libqt5webenginecore5 5.14.2+dfsg1-5 thanks Hey, Since you can reproduce this with Falkon, it definitely isn't an issue in qutebrowser. Reassigning this to QtWebEngine. Let's hope it works, I'm not too experienced with using Debian's BTS - whoever is on the receiving end, please let me know if I messed up something :) On Mon, Sep 21, 2020 at 05:57:03PM -0300, felipe wrote: > Attaching 'coredump info temp-basedir with dbgsym.txt' > and 'coredump info qt-flag single-process with dbgsym'. Thanks! For reference, here's a demangled version of the relevant stack trace: #0 0x7f6842b6928f blink::CompositedLayerMapping::ComputeBoundsOfOwningLayer(blink::PaintLayer const*, blink::IntRect&, blink::IntRect&, blink::PhysicalOffset&, blink::IntPoint&) (libQt5WebEngineCore.so.5 0x462928f) #1 0x7f6842b74054 blink::CompositedLayerMapping::UpdateGraphicsLayerGeometry(blink::PaintLayer const*, blink::PaintLayer const*, WTF::Vector&, blink::GraphicsLayerUpdater::UpdateContext&) (libQt5WebEngineCore.so.5 0x4634054) #2 0x7f6842b76561 blink::GraphicsLayerUpdater::UpdateRecursive(blink::PaintLayer&, blink::GraphicsLayerUpdater::UpdateType, blink::GraphicsLayerUpdater::UpdateContext&, WTF::Vector&) (libQt5WebEngineCore.so.5 0x4636561) #3 0x7f6842b764ca blink::GraphicsLayerUpdater::UpdateRecursive(blink::PaintLayer&, blink::GraphicsLayerUpdater::UpdateType, blink::GraphicsLayerUpdater::UpdateContext&, WTF::Vector&) (libQt5WebEngineCore.so.5 0x46364ca) #4 0x7f6842b764ca blink::GraphicsLayerUpdater::UpdateRecursive(blink::PaintLayer&, blink::GraphicsLayerUpdater::UpdateType, blink::GraphicsLayerUpdater::UpdateContext&, WTF::Vector&) (libQt5WebEngineCore.so.5 0x46364ca) #5 0x7f6842b764ca blink::GraphicsLayerUpdater::UpdateRecursive(blink::PaintLayer&, blink::GraphicsLayerUpdater::UpdateType, blink::GraphicsLayerUpdater::UpdateContext&, WTF::Vector&) (libQt5WebEngineCore.so.5 0x46364ca) #6 0x7f6842b764ca blink::GraphicsLayerUpdater::UpdateRecursive(blink::PaintLayer&, blink::GraphicsLayerUpdater::UpdateType, blink::GraphicsLayerUpdater::UpdateContext&, WTF::Vector&) (libQt5WebEngineCore.so.5 0x46364ca) #7 0x7f6842b766bd blink::GraphicsLayerUpdater::Update(blink::PaintLayer&, WTF::Vector&) (libQt5WebEngineCore.so.5 0x46366bd) #8 0x7f6842b76b3d blink::PaintLayerCompositor::UpdateIfNeeded(blink::DocumentLifecycle::LifecycleState, blink::CompositingReasonsStats&) (libQt5WebEngineCore.so.5 0x4636b3d) #9 0x7f6842b780d0 blink::PaintLayerCompositor::UpdateIfNeededRecursiveInternal(blink::DocumentLifecycle::LifecycleState, blink::CompositingReasonsStats&) (libQt5WebEngineCore.so.5 0x46380d0) #10 0x7f6842b78409 blink::PaintLayerCompositor::UpdateIfNeededRecursive(blink::DocumentLifecycle::LifecycleState) (libQt5WebEngineCore.so.5 0x4638409) #11 0x7f6842579377 blink::LocalFrameView::RunCompositingLifecyclePhase(blink::DocumentLifecycle::LifecycleState) (libQt5WebEngineCore.so.5 0x4039377) #12 0x7f68425839d9 blink::LocalFrameView::UpdateLifecyclePhasesInternal(blink::DocumentLifecycle::LifecycleState).part.0 (libQt5WebEngineCore.so.5 0x40439d9) #13 0x7f6842583e14 blink::LocalFrameView::UpdateLifecyclePhases(blink::DocumentLifecycle::LifecycleState, blink::DocumentLifecycle::LifecycleUpdateReason) (libQt5WebEngineCore.so.5 0x4043e14) #14 0x7f6842b11564 blink::PageAnimator::UpdateAllLifecyclePhases(blink::LocalFrame&, blink::DocumentLifecycle::LifecycleUpdateReason) (libQt5WebEngineCore.so.5 0x45d1564) #15 0x7f68424cf16c blink::WebViewImpl::UpdateLifecycle(blink::WebWidget::LifecycleUpdate, blink::WebWidget::LifecycleUpdateReason) (libQt5WebEngineCore.so.5 0x3f8f16c) #16 0x7f684332cafa content::RenderWidget::UpdateVisualState() (libQt5WebEngineCore.so.5 0x4decafa) #17 0x7f68416a92c6 cc::ProxyMain::BeginMainFrame(std::unique_ptr >) (libQt5WebEngineCore.so.5 0x31692c6) #18 0x7f68416a1633 base::internal::Invoker >), base::WeakPtr, std::unique_ptr > >, void ()>::RunOnce(base::internal::BindStateBase*) (libQt5WebEngineCore.so.5 0x3161633) #19 0x7f6840b043a4 base::TaskAnnotator::RunTask(char const*, base::PendingTask*) (libQt5WebEngineCore.so.5 0x25c43a4) #20 0x7f6840b17337 base::sequence_manager::internal::ThreadControllerWithMessagePumpImpl::DoWorkImpl(base::sequence_manager::LazyNow*, bool*) (libQt5WebEngineCore.so.5 0x25d7337) #21 0x7f6840b177b8 base::sequence_manager::internal::ThreadControllerWithMessagePumpImpl::DoSomeWork() (libQt5WebEngineCore.so.5 0x25d77b8) #22 0x7f6840acdba6 base::MessagePumpDefault::Run(base::MessagePump::Delegate*) (libQt5WebEngineCore.so.5 0x258dba6) #23 0x7f6840b14cdf base::sequence_manager::internal::ThreadControllerWithMessagePumpImpl::Run(bool, base::TimeDelta) (libQt5WebEngineCore.so.5 0x25d4cdf)
Bug#970478: ERROR: Renderer process crashed when using qtwebengine backend.
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 ;)
> [...]
>
>
> Thread 40 "Chrome_InProcRe" received signal SIGILL, Illegal instruction.
> [Switching to Thread 0x7fff58a89700 (LWP 12375)]
> 0x7fffea1b128f 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 0x7fffea1b128f 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 0x7fffea1bc054 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
Bug#970478: ERROR: Renderer process crashed when using qtwebengine backend.
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'
> (If there are no debug symbols available at all, I wonder if a bug should
> be opened against libqt5webengine5a - Axel/Fritz, if you have an opinion
> on that, I'd like to hear more)
>
> 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
(No debugging symbols found in /usr/bin/python3)
Starting program: /usr/bin/python3 -m qutebrowser --temp-basedir --qt-flag
single-process
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[Detaching after fork from child process 12318]
[New Thread 0x7fffdd4e2700 (LWP 12329)]
12:12:36 WARNING: QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to
'/tmp/runtime-root'
[New Thread 0x7fffd075c700 (LWP 12332)]
[New Thread 0x7fffcff5b700 (LWP 12333)]
[New Thread 0x7fffcf75a700 (LWP 12334)]
[New Thread 0x7fffcef59700 (LWP 12335)]
[New Thread 0x7fffce758700 (LWP 12336)]
[New Thread 0x7fffcdf57700 (LWP 12337)]
[New Thread 0x7fffcd756700 (LWP 12338)]
[New Thread 0x7fffccf55700 (LWP 12339)]
[New Thread 0x7fffa700 (LWP 12340)]
[New Thread 0x7fffaf7fe700 (LWP 12341)]
[New Thread 0x7fffaeffd700 (LWP 12342)]
[New Thread 0x7fffae7fc700 (LWP 12343)]
[New Thread 0x7fffadffb700 (LWP 12344)]
[New Thread 0x7fffad7fa700 (LWP 12345)]
[New Thread 0x7fffacff9700 (LWP 12346)]
[New Thread 0x7fff8bfff700 (LWP 12347)]
[Detaching after fork from child process 12348]
[New Thread 0x7fff8b7fe700 (LWP 12349)]
[Thread 0x7fff8b7fe700 (LWP 12349) exited]
[New Thread 0x7fff8b7fe700 (LWP 12350)]
[New Thread 0x7fff8a470700 (LWP 12351)]
[New Thread 0x7fff89c6f700 (LWP 12352)]
[New Thread 0x7fff8946e700 (LWP 12353)]
[New Thread 0x7fff88c6d700 (LWP 12354)]
[New Thread 0x7fff73fff700 (LWP 12355)]
[New Thread 0x7fff737fe700 (LWP 12356)]
[New Thread 0x7fff72ffd700 (LWP 12357)]
[New Thread 0x7fff717e6700 (LWP 12358)]
[New Thread 0x7fff70fe5700 (LWP 12359)]
[New Thread 0x7fff5bfff700 (LWP 12360)]
[New Thread 0x7fff5b7fe700 (LWP 12361)]
[New Thread 0x7fff5affd700 (LWP 12362)]
[Thread 0x7fff5affd700 (LWP 12362) exited]
[New Thread 0x7fff5affd700 (LWP 12363)]
[Thread 0x7fff5affd700 (LWP 12363) exited]
[New Thread 0x7fff5affd700 (LWP 12364)]
[New Thread 0x7fff5a7fc700 (LWP 12365)]
[New Thread 0x7fff59ffb700 (LWP 12366)]
[New Thread 0x7fff597fa700 (LWP 12367)]
[Detaching after fork from child process 12368]
[New Thread 0x7fff727fc700 (LWP 12373)]
[New Thread 0x7fff71ffb700 (LWP 12374)]
[New Thread 0x7fff58a89700 (LWP 12375)]
[New Thread 0x7fff27fff700 (LWP 12376)]
[New Thread 0x7fff277fe700 (LWP 12377)]
[New Thread 0x7fff26ffd700 (LWP 12378)]
[New Thread 0x7fff267fc700 (LWP 12379)]
[New Thread 0x7fff25ffb700 (LWP 12380)]
[New Thread 0x7fff257fa700 (LWP 12381)]
[New Thread 0x7fff24ff9700 (LWP 12382)]
[New Thread 0x7fff07fff700 (LWP 12383)]
[New Thread 0x7ffef700 (LWP 12384)]
[New Thread 0x7fff077fe700 (LWP 12385)]
[New Thread 0x7fff06ffd700 (LWP 12386)]
[New Thread 0x7fff063fc700 (LWP 12387)]
--Type for more, q to quit, c to continue without paging--
Thread 40 "Chrome_InProcRe" received signal SIGILL, Illegal instruction.
[Switching to Thread 0x7fff58a89700 (LWP 12375)]
0x7fffea1b128f 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
Bug#970478: ERROR: Renderer process crashed when using qtwebengine backend.
Attachments were missings last time. libaom0-dbgsym libasound2-dbgsym libavcodec58-dbgsym libavformat58-dbgsym libavutil56-dbgsym libblkid1-dbgsym libbluray2-dbgsym libbrotli1-dbgsym libbsd0-dbgsym libbz2-1.0-dbgsym libc6-dbg libcairo-gobject2-dbgsym libcairo2-dbgsym libchromaprint1-dbgsym libcodec2-0.9-dbgsym libcom-err2-dbgsym libdatrie1-dbgsym libdav1d4-dbgsym libdbus-1-3-dbgsym libdouble-conversion3-dbgsym libdrm2-dbgsym libevent-2.1-7-dbgsym libexpat1-dbgsym libffi7-dbgsym libfontconfig1-dbgsym libfreetype6-dbgsym libfribidi0-dbgsym libgcc-s1-dbgsym libgcrypt20-dbgsym libgdk-pixbuf2.0-0-dbgsym libgl1-dbgsym libglib2.0-0-dbgsym libglvnd0-dbgsym libglx0-dbgsym libgme0-dbgsym libgmp10-dbgsym libgnutls30-dbgsym libgomp1-dbgsym libgpg-error0-dbgsym libgraphite2-3-dbgsym libgsm1-dbgsym libharfbuzz0b-dbgsym libhogweed6-dbgsym libicu67-dbgsym libidn2-0-dbgsym libjpeg62-turbo-dbgsym libkeyutils1-dbgsym libkrb5-dbg liblcms2-2-dbgsym liblz4-1-dbgsym liblzma5-dbgsym libmd4c0-dbgsym libmfx1-dbgsym libminizip1-dbgsym libmount1-dbgsym libmp3lame0-dbgsym libmpg123-0-dbgsym libnettle8-dbgsym libnorm1-dbgsym libnspr4-dbgsym libnss3-dbgsym libnuma1-dbgsym libogg-dbg libopenjp2-7-dbgsym libopenmpt0-dbgsym libopus-dbg libp11-kit0-dbgsym libpango-1.0-0-dbgsym libpangocairo-1.0-0-dbgsym libpangoft2-1.0-0-dbgsym libpcre2-16-0-dbgsym libpcre2-8-0-dbgsym libpcre3-dbg libpgm-5.2-0-dbgsym libpixman-1-0-dbgsym libpng16-16-dbgsym libqt5core5a-dbgsym libqt5gui5-dbgsym libqt5network5-dbgsym libqt5positioning5-dbgsym libqt5qml5-dbgsym libqt5qmlmodels5-dbgsym libqt5quick5-dbgsym libqt5test5-dbgsym libqt5webchannel5-dbgsym libqt5webengine5-dbgsym libqt5webenginecore5-dbgsym librabbitmq4-dbgsym libre2-8-dbgsym librsvg2-2-dbgsym libselinux1-dbgsym libshine3-dbgsym libsnappy1v5-dbgsym libsodium23-dbgsym libsoxr0-dbgsym libspeex-dbg libsrt1-gnutls-dbgsym libssh-gcrypt-4-dbgsym libssl1.1-dbgsym libstdc++6-dbgsym libswresample3-dbgsym libsystemd0-dbgsym libtasn1-6-dbgsym libthai0-dbgsym libtheora0-dbgsym libtwolame0-dbgsym libunistring2-dbgsym libuuid1-dbgsym libva-drm2-dbgsym libva-x11-2-dbgsym libva2-dbgsym libvdpau1-dbgsym libvorbis0a-dbgsym libvorbisenc2-dbgsym libvorbisfile3-dbgsym libvpx6-dbgsym libwavpack1-dbgsym libwebp6-dbgsym libwebpdemux2-dbgsym libwebpmux3-dbgsym libx11-6-dbgsym libx264-160-dbgsym libx265-192-dbgsym libxau6-dbg libxcb-render0-dbgsym libxcb-shm0-dbgsym libxcb1-dbgsym libxcomposite1-dbgsym libxdamage1-dbgsym libxdmcp6-dbg libxext6-dbg libxfixes3-dbgsym libxml2-dbgsym libxrender1-dbgsym libxslt1.1-dbgsym libxss1-dbgsym libxvidcore4-dbgsym libzmq5-dbgsym libzstd1-dbgsym libzvbi0-dbgsym ocl-icd-libopencl1-dbgsym zlib1g-dbgsym PID: 5850 (qutebrowser) UID: 1000 (felipe) GID: 1000 (felipe) Signal: 4 (ILL) Timestamp: Mon 2020-09-21 11:41:40 -03 (39s ago) Command Line: /usr/bin/python3 /usr/bin/qutebrowser --qt-flag single-process Executable: /usr/bin/python3.8 Control Group: /user.slice/user-1000.slice/session-1.scope Unit: session-1.scope Slice: user-1000.slice Session: 1 Owner UID: 1000 (felipe) Boot ID: 8a493cc1f411446a9c0bc0e0d42580f6 Machine ID: 70dd67e312f741bc93a178be9523797f Hostname: fx8350 Storage: /var/lib/systemd/coredump/core.qutebrowser.1000.8a493cc1f411446a9c0bc0e0d42580f6.5850.16006993.zst Message: Process 5850 (qutebrowser) of user 1000 dumped core. Stack trace of thread 5894: #0 0x7f4c837b3fe1 raise (libpthread.so.0 + 0x13fe1) #1 0x7f4c837b4140 __restore_rt (libpthread.so.0 + 0x14140) #2 0x7f4c757c928f n/a (libQt5WebEngineCore.so.5 + 0x462928f) #3 0x7f4c757d4054 n/a (libQt5WebEngineCore.so.5 + 0x4634054) #4 0x7f4c757d6561 n/a (libQt5WebEngineCore.so.5 + 0x4636561) #5 0x7f4c757d64ca n/a (libQt5WebEngineCore.so.5 + 0x46364ca) #6 0x7f4c757d64ca n/a (libQt5WebEngineCore.so.5 + 0x46364ca) #7 0x7f4c757d64ca n/a (libQt5WebEngineCore.so.5 + 0x46364ca) #8 0x7f4c757d64ca n/a (libQt5WebEngineCore.so.5 + 0x46364ca) #9 0x7f4c757d66bd n/a (libQt5WebEngineCore.so.5 + 0x46366bd) #10 0x7f4c757d6b3d n/a (libQt5WebEngineCore.so.5 + 0x4636b3d) #11 0x7f4c757d80d0 n/a (libQt5WebEngineCore.so.5 + 0x46380d0) #12 0x7f4c757d8409 n/a (libQt5WebEngineCore.so.5 + 0x4638409) #13 0x7f4c751d9377 n/a (libQt5WebEngineCore.so.5 + 0x4039377) #14 0x7f4c751e39d9 n/a (libQt5WebEngineCore.so.5 + 0x40439d9) #15 0x7f4c751e3e14 n/a (libQt5WebEngineCore.so.5 + 0x4043e14) #16 0x7f4c75771564 n/a (libQt5WebEngineCore.so.5 + 0x45d1564) #17 0x7f4c7512f16c n/a (libQt5WebEngineCore.so.5
Bug#970478: ERROR: Renderer process crashed when using qtwebengine backend.
Hi,
Florian Bruhin wrote:
> However, I'm not sure about how things look in Debian exactly:
>
> 1) Whether coredumpctl is in use
Don't know either, I don't use systemd... For non-systemd systems, you
can install e.g. corekeeper which makes coredumps to be saved in
/var/crash/$pid/.
> 2) How to get debug symbols for the libqt5webengine5 package
# apt install debian-goodies
to get find-dbgsym-packages, and then continue as Florian already
mostly found out:
> For 2), it looks like there's no libqt5webengine5-dbg{,sym} package in
> the debian archives.
*-dbgsym packages are never in the default archive and always in the
dedicated debian-debug archive. And there they are:
libqt5webengine5-dbgsym - debug symbols for libqt5webengine5
Hence you need to add that repo if you haven't already:
> 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
That URL + find-dbgsym-packages is the right way. :-)
> (If there are no debug symbols available at all, I wonder if a bug should
> be opened against libqt5webengine5a - Axel/Fritz, if you have an opinion
> on that, I'd like to hear more)
Not yet, but probably no qutebrowser issue.
Regards, Axel (partially with the find-dbgsym-packages maintainer hat on :-)
--
,''`. | Axel Beckert , https://people.debian.org/~abe/
: :' : | Debian Developer, ftp.ch.debian.org Admin
`. `' | 4096R: 2517 B724 C5F6 CA99 5329 6E61 2FF9 CD59 6126 16B5
`-| 1024D: F067 EA27 26B9 C3FC 1486 202E C09E 1D89 9593 0EDE
Bug#970478: ERROR: Renderer process crashed when using qtwebengine backend.
Hey,
On Mon, Sep 21, 2020 at 10:00:50AM -0300, felipe wrote:
> And dmesg shows this line for each time i refresh or try to open any website:
>traps: QtWebEngineProc[4369] trap invalid opcode ip:7f322fa7128f
> sp:7ffd1d00c600 error:0 in
> libQt5WebEngineCore.so.5.14.2[7f322bd14000+5a63000]
I think I'll need a C++ stacktrace to say more about what's happening.
However, I'm not sure about how things look in Debian exactly:
1) Whether coredumpctl is in use
2) How to get debug symbols for the libqt5webengine5 package
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"?
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
(If there are no debug symbols available at all, I wonder if a bug should
be opened against libqt5webengine5a - Axel/Fritz, if you have an opinion
on that, I'd like to hear more)
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
And then use "bt" when you get the (gdb) prompt? Let's hope it says
something useful even without debugging symbols...
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
Bug#970478: ERROR: Renderer process crashed when using qtwebengine backend.
Hey, Florian! On 9/21/20 7:57 AM, Florian Bruhin wrote: > Hey, > > Upstream maintainer here - not sure what's going on exactly, but let's > try to find out :) That's awesome, thank you. > On Wed, Sep 16, 2020 at 09:12:19PM -0300, zeden wrote: >> Trying to open sites using qtwebengine backend results in: >> "ERROR: Renderer process crashed". > > I assume you're seeing this on any webpage you open? Yes. It happens on any webpage. > If you start qutebrowser in a terminal and with --temp-basedir, does it > happen as well? If so, do you see anything interesting in the output > there? Starting from terminal with: $ qutebrowser --temp-basedir 09:53:21 ERROR: Renderer process crashed When I quit with, the console shows: [4324:4350:0921/095326.040068:ERROR:database.cc(1598)] Cookie sqlite error 1032, errno 0: attempt to write a readonly database, sql: INSERT INTO cookies (creation_utc, host_key, name, value, encrypted_value, path, expires_utc, is_secure, is_httponly, samesite, last_access_utc, has_expires, is_persistent, priority) VALUES (?,?,?,?,?,?,?,?,?,?,?,?,?,?) [4324:4350:0921/095326.0400 And dmesg shows this line for each time i refresh or try to open any website: traps: QtWebEngineProc[4369] trap invalid opcode ip:7f322fa7128f sp:7ffd1d00c600 error:0 in libQt5WebEngineCore.so.5.14.2[7f322bd14000+5a63000] Thank you in advance!
Bug#970478: ERROR: Renderer process crashed when using qtwebengine backend.
Hey, Upstream maintainer here - not sure what's going on exactly, but let's try to find out :) On Wed, Sep 16, 2020 at 09:12:19PM -0300, zeden wrote: > Trying to open sites using qtwebengine backend results in: > "ERROR: Renderer process crashed". I assume you're seeing this on any webpage you open? If you start qutebrowser in a terminal and with --temp-basedir, does it happen as well? If so, do you see anything interesting in the output there? 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
Bug#970478: ERROR: Renderer process crashed when using qtwebengine backend.
Package: qutebrowser-qtwebengine Version: 1.13.1-1 Severity: important X-Debbugs-Cc: ze...@riseup.net Dear Maintainer, Trying to open sites using qtwebengine backend results in: "ERROR: Renderer process crashed". Hitting the "Try again" button or reloading does not resolve the issue. Launching from terminal with: $ qutebrowser --backend webkit makes the browser work again. I have cleared cache, config and reinstalled qutebrowser. Checking dmesg, the only relevant message is: [ +23.172585] traps: QtWebEngineProc[14326] trap invalid opcode ip:7f84ed8f928f sp:7ffc29e4afd0 error:0 in libQt5WebEngineCore.so.5.14.2[7f84e9b9c000+5a63000] -- System Information: Debian Release: bullseye/sid APT prefers unstable APT policy: (990, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.8.0-1-amd64 (SMP w/8 CPU threads) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages qutebrowser-qtwebengine depends on: ii libqt5webenginecore5 5.14.2+dfsg1-5 ii python3-pyqt5.qtwebengine 5.15.0-1+b1 ii qutebrowser1.13.1-1 qutebrowser-qtwebengine recommends no packages. qutebrowser-qtwebengine suggests no packages. -- no debconf information
