Description of problem:
Random tab crash in qutebrowser. Not entirely sure what caused it.
Version-Release number of selected component:
cmdline: /usr/lib64/qt5/libexec/QtWebEngineProcess --type=renderer --disable-gpu-memory-buffer-video-frames --enable-threaded-compositing --reduced-referrer-granularity --use-gl=egl --enable-features=AllowContentInitiatedDataUrlNavigations --disable-features=BackgroundFetch,MojoVideoCapture,SurfaceSynchronization,UsePdfCompositorServiceForPrint,UserActivationV2,VizDisplayCompositor --service-pipe-token=18211343968319505486 --lang=en-GB --webengine-schemes=qute:lL;qrc:sLV --num-raster-threads=4 --enable-main-frame-before-activation --service-request-channel-token=18211343968319505486 --renderer-client-id=52 --shared-files
runlevel: N 5
Thread no. 1 (10 frames)
#0 sandbox::CrashSIGSYS_Handler at ../../3rdparty/chromium/sandbox/linux/seccomp-bpf-helpers/sigsys_handlers.cc:218
#1 sandbox::Trap::SigSys at ../../3rdparty/chromium/sandbox/linux/seccomp-bpf/trap.cc:244
#3 __clock_nanosleep at ../sysdeps/unix/sysv/linux/clock_nanosleep.c:48
#4 __nanosleep at nanosleep.c:27
#5 base::PlatformThread::Sleep at ./../../3rdparty/chromium/base/threading/platform_thread_posix.cc:233
#6 base::subtle::SpinLock::LockSlow at ./../../3rdparty/chromium/base/allocator/partition_allocator/spin_lock.cc:97
#7 WTF::StringImpl::CreateUninitialized(unsigned int, unsigned char*&)
#8 WTF::StringImpl::Create(unsigned char const*, unsigned int)
#9 WTF::String::String(char const*, unsigned long)
#10 blink::ResourceRequest::ResourceRequest(blink::KURL const&)
Created attachment 1669250 [details]
Created attachment 1669251 [details]
Created attachment 1669252 [details]
Created attachment 1669253 [details]
Created attachment 1669254 [details]
Created attachment 1669255 [details]
Created attachment 1669256 [details]
Created attachment 1669257 [details]
Created attachment 1669258 [details]
Created attachment 1669259 [details]
Seeing this quite often now. I'll be happy to provide more info---just not sure how to debug it at the moment.
Frequent crashes using ask.fedoraproject.org, if someone wishes to try and reproduce them.
Similar problem has been detected:
Another random crash
cmdline: /usr/lib64/qt5/libexec/QtWebEngineProcess --type=renderer --disable-gpu-memory-buffer-video-frames --enable-threaded-compositing --reduced-referrer-granularity --use-gl=egl --enable-features=AllowContentInitiatedDataUrlNavigations --disable-features=BackgroundFetch,MojoVideoCapture,SurfaceSynchronization,UsePdfCompositorServiceForPrint,UserActivationV2,VizDisplayCompositor --service-pipe-token=5450357993492127767 --lang=en-GB --webengine-schemes=qute:lL;qrc:sLV --num-raster-threads=4 --enable-main-frame-before-activation --service-request-channel-token=5450357993492127767 --renderer-client-id=64 --shared-files
reason: QtWebEngineProcess killed by SIGSEGV
runlevel: N 5
I was able to reproduce the crashes on twitter.com in falkon also.
Is there someplace upstream I can report and help debug this perhaps?
Just a note, removing the freeworld package does not fix the crashes. Still seeing them.
Rex, sorry: any ideas here? Can I provide more information to help somehow?
Upstream is qt.io , bugs => https://bugreports.qt.io/
Thanks, Rex! I've filed it upstream too now: https://bugreports.qt.io/browse/QTBUG-83054
Perhaps related to this: https://bugzilla.redhat.com/show_bug.cgi?id=1773289 which was reported upstream with a patch also https://bugreports.qt.io/browse/QTBUG-81313
Something to do with glibc
It seems to be that particular issue. It's already fixed with patches for the various branches:
I don't know what chromium branch 5.13.2 is based off, though, so I don't know what patch to try to test :/
We need https://chromium.googlesource.com/chromium/src/+/54407b422a9cbf775a68c1d57603c0ecac8ce0d7 backported or, ideally, QtWebEngine upgraded to at least 5.14.1.
There are 4 patches here on the qt.io bug report: https://bugreports.qt.io/browse/QTBUG-81313
I've requested them to tell me which one I can try with 5.13.2---I'll see if I can apply it in the spec and test here, as a fix to make the browsers usable again.
I expect updating to 5.14 is quite a task requiring lots of package rebuilds etc? I can help with the rebuilds, but all the patching and backporting would be beyond me since I don't know enough of the Qt dev system/life cycle etc.
QtWebEngine can be upgraded separately from the rest of Qt. That said, it is the package that requires the most work to upgrade, as far as the packaging itself (not the rebuild of reverse dependencies) is concerned.
Opened a PR: https://src.fedoraproject.org/rpms/qt5-qtwebengine/pull-request/5
Thanks! PR merged, builds underway.
Aside, I've been working on 5.14.1 on/off over the past week or so, making good progress, hopefully will get that imported soonish. Latest scratch build attempt:
Thank you! I'll be happy to test 5.14.1 when you think it's testable too.
*** Bug 1818593 has been marked as a duplicate of this bug. ***
FEDORA-2020-16421b19ed has been submitted as an update to Fedora 32. https://bodhi.fedoraproject.org/updates/FEDORA-2020-16421b19ed
FEDORA-2020-16421b19ed has been pushed to the Fedora 32 testing repository.
In short time you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2020-16421b19ed`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2020-16421b19ed
See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2020-16421b19ed has been pushed to the Fedora 32 stable repository.
If problem still persists, please make note of it in this bug report.