I launched chromium with: chromium --enable-logging=stderr chrome://gpu 2>&1 | tee 1853731.txt
... then kept an eye on it. Once it got stuck and stopped rendering things, I found the attached portion repeating until I killed it off with killall chrome. I could initially still open a new tab and go to youtube, but I can provide more of the capture if need be, though I was mindful it had some session IDs etc. in it. Before the point at which I noticed the error, and the logs went crazy, I also observed things like: [9001:9001:1219/203419.593465:WARNING:x11_util.cc(1417)] X error received: serial 9326, error_code 3 (BadWindow), request_code 3, minor_code 0 (Unknown) ** Attachment added: "Exerpt of enable-logging=stderr output at time of crash" https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1853731/+attachment/5313998/+files/1853731-exerpt.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1853731 Title: [snap] chromium stops working after a while, fails to render new tabs/pages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1853731/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
