Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.
Bug 1812482
Summary: | Fedora 32 qtwebengine crashes: affects both qutebrowser and falkon: [abrt] qt5-qtwebengine: sandbox::CrashSIGSYS_Handler(): QtWebEngineProcess killed by SIGSEGV | ||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Ankur Sinha (FranciscoD) <sanjay.ankur> | ||||||||||||||||||||||
Component: | qt5-qtwebengine | Assignee: | Rex Dieter <rdieter> | ||||||||||||||||||||||
Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||||||||||||||||||
Severity: | unspecified | Docs Contact: | |||||||||||||||||||||||
Priority: | unspecified | ||||||||||||||||||||||||
Version: | 32 | CC: | flouhl, kde-sig, kevin, pmkellly, rdieter | ||||||||||||||||||||||
Target Milestone: | --- | ||||||||||||||||||||||||
Target Release: | --- | ||||||||||||||||||||||||
Hardware: | x86_64 | ||||||||||||||||||||||||
OS: | Unspecified | ||||||||||||||||||||||||
URL: | https://retrace.fedoraproject.org/faf/reports/bthash/e43e9c368e8d83f2c35888581cff03f9057aeb4d | ||||||||||||||||||||||||
Whiteboard: | abrt_hash:442868511cd1b2afceda037534b47c2120a1d0b7;VARIANT_ID=workstation; | ||||||||||||||||||||||||
Fixed In Version: | qt5-qtwebengine-5.13.2-4.fc32 | Doc Type: | If docs needed, set a value | ||||||||||||||||||||||
Doc Text: | Story Points: | --- | |||||||||||||||||||||||
Clone Of: | Environment: | ||||||||||||||||||||||||
Last Closed: | 2020-03-31 00:17:28 UTC | Type: | --- | ||||||||||||||||||||||
Regression: | --- | Mount Type: | --- | ||||||||||||||||||||||
Documentation: | --- | CRM: | |||||||||||||||||||||||
Verified Versions: | Category: | --- | |||||||||||||||||||||||
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||||||||||||||||||
Cloudforms Team: | --- | Target Upstream Version: | |||||||||||||||||||||||
Embargoed: | |||||||||||||||||||||||||
Attachments: |
|
Description
Ankur Sinha (FranciscoD)
2020-03-11 12:23:46 UTC
Created attachment 1669250 [details]
File: backtrace
Created attachment 1669251 [details]
File: core_backtrace
Created attachment 1669252 [details]
File: cpuinfo
Created attachment 1669253 [details]
File: dso_list
Created attachment 1669254 [details]
File: environ
Created attachment 1669255 [details]
File: exploitable
Created attachment 1669256 [details]
File: limits
Created attachment 1669257 [details]
File: maps
Created attachment 1669258 [details]
File: open_fds
Created attachment 1669259 [details]
File: proc_pid_status
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 reporter: libreport-2.12.0 backtrace_rating: 4 cgroup: 0::/user.slice/user-1000.slice/user/gnome-launched-org.qutebrowser.qutebrowser.desktop-15401.scope 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 crash_function: sandbox::CrashSIGSYS_Handler executable: /usr/lib64/qt5/libexec/QtWebEngineProcess journald_cursor: s=936fe99be74f4f4880cb7004afd66f6a;i=3b89;b=d291693d7eaa4246ad9c2117b29f2a1e;m=163d0fc1c;t=5a126969aaa5d;x=f5572a21309aaefb kernel: 5.6.0-0.rc5.git0.2.fc32.x86_64 mountinfo: package: qt5-qtwebengine-5.13.2-3.fc32 reason: QtWebEngineProcess killed by SIGSEGV rootdir: /proc/15665/fdinfo runlevel: N 5 type: CCpp uid: 1000 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: https://bugreports.qt.io/browse/QTBUG-81313 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. 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: https://koji.fedoraproject.org/koji/taskinfo?taskID=42762429 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 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. |