Details
-
Type:
Bug
-
Status: Closed
-
Priority:
P1: Critical
-
Resolution: Done
-
Affects Version/s: 5.14.0
-
Fix Version/s: 5.12.8, 5.14.1, 5.15.0 Alpha
-
Component/s: WebEngine
-
Labels:None
-
Platform/s:
Linux/X11
-
Commits:7b1e74a4c41b6ba3adca2caea8e45c1f314a70d7 (qt/qtwebengine/5.14.1)
Description
It looks like glibc 2.30.9000-18 introduced clock_nanosleep which Chromium's sandbox doesn't allow, causing immediate renderer process crashes.
Background:
- https://bugzilla.redhat.com/show_bug.cgi?id=1773289
- https://bugs.chromium.org/p/chromium/issues/detail?id=1025739
Fix:
I tried applying the commit on 77-based, but chromium/sandbox/linux/seccomp-bpf-helpers/syscall_parameters_restrictions.h doesn't seem to apply cleanly. I didn't investigate further at that point.
Attachments
Issue Links
- is duplicated by
-
-
- Closed
-
| For Gerrit Dashboard: QTBUG-81313 | ||||||
|---|---|---|---|---|---|---|
| # | Subject | Branch | Project | Status | CR | V |
| 286946,2 | [Backport] Allow restricted clock_nanosleep in Linux sandbox | 77-based | qt/qtwebengine-chromium | Status: MERGED | +2 | 0 |
| 286999,2 | Update Chromium | 5.14.1 | qt/qtwebengine | Status: MERGED | +2 | 0 |
| 292345,2 | [Backport] Allow restricted clock_nanosleep in Linux sandbox | 79-based | qt/qtwebengine-chromium | Status: MERGED | +2 | 0 |
| 292352,2 | [Backport] Allow restricted clock_nanosleep in Linux sandbox | 69-based | qt/qtwebengine-chromium | Status: MERGED | +2 | 0 |