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 0x00007f6842b6928f > > blink::CompositedLayerMapping::ComputeBoundsOfOwningLayer(blink::PaintLayer > > const*, blink::IntRect&, blink::IntRect&, blink::PhysicalOffset&, > > blink::IntPoint&) (libQt5WebEngineCore.so.5 0x462928f) > > #1 0x00007f6842b74054 > > blink::CompositedLayerMapping::UpdateGraphicsLayerGeometry(blink::PaintLayer > > const*, blink::PaintLayer const*, WTF::Vector<blink::PaintLayer*, 0u, > > WTF::PartitionAllocator>&, blink::GraphicsLayerUpdater::UpdateContext&) > > (libQt5WebEngineCore.so.5 0x4634054) > > #2 0x00007f6842b76561 > > blink::GraphicsLayerUpdater::UpdateRecursive(blink::PaintLayer&, > > blink::GraphicsLayerUpdater::UpdateType, > > blink::GraphicsLayerUpdater::UpdateContext&, > > WTF::Vector<blink::PaintLayer*, 0u, WTF::PartitionAllocator>&) > > (libQt5WebEngineCore.so.5 0x4636561) > > #3 0x00007f6842b764ca > > blink::GraphicsLayerUpdater::UpdateRecursive(blink::PaintLayer&, > > blink::GraphicsLayerUpdater::UpdateType, > > blink::GraphicsLayerUpdater::UpdateContext&, > > WTF::Vector<blink::PaintLayer*, 0u, WTF::PartitionAllocator>&) > > (libQt5WebEngineCore.so.5 0x46364ca) > > #4 0x00007f6842b764ca > > blink::GraphicsLayerUpdater::UpdateRecursive(blink::PaintLayer&, > > blink::GraphicsLayerUpdater::UpdateType, > > blink::GraphicsLayerUpdater::UpdateContext&, > > WTF::Vector<blink::PaintLayer*, 0u, WTF::PartitionAllocator>&) > > (libQt5WebEngineCore.so.5 0x46364ca) > > #5 0x00007f6842b764ca > > blink::GraphicsLayerUpdater::UpdateRecursive(blink::PaintLayer&, > > blink::GraphicsLayerUpdater::UpdateType, > > blink::GraphicsLayerUpdater::UpdateContext&, > > WTF::Vector<blink::PaintLayer*, 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). 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
