When a glibc update accidentally breaks Chromium's audio (2021)
Web page · https://refi64.dev/posts/chromium-audio-break.html
First seen by Oriel on .
AI summary
The post traces Chromium audio crashes after a Flatpak runtime upgrade to a glibc 2.33 change that exposed a flag-handling bug in Chromium’s audio sandbox.
- The failure occurred when libpulse waited on condition variables in Chromium’s sandboxed audio service; disabling AudioServiceSandbox stopped the crash.
- glibc 2.33 refactored pthread condition-variable waits to use __futex_abstimed_wait_cancelable64 even without a timeout, passing clockid 0, which is CLOCK_REALTIME.
- That path added FUTEX_CLOCK_REALTIME to futex_time64 operations, while Chromium’s BPF policy removed only FUTEX_PRIVATE_FLAG before checking allowed operations.
- The resulting operation was rejected with EPERM, which glibc treated as an unexpected futex error and used to abort the audio process.
- The issue appeared in Chromium because its AudioServiceSandboxLinux field trial was active; Chrome, Brave, and Edge did not report the same trial.
#glibc #chromium #linux sandbox #pulseaudio
Generated by gpt-5.6-sol. Check the original for details.
Metric trends
Last 30 days · Up to 120 recorded samples per source and metric, with reposts kept separate · First and latest retained
Points
Score reported by the source.
- Lobsters: 22, latest observation ; +21 over observed period since
Comments
Comment count reported by the source.
- Lobsters: 2, latest observation ; +2 over observed period since
Aliases
| Source | External ID | URL |
|---|---|---|
| Lobsters | 5ullyu | https://refi64.dev/posts/chromium-audio-break.html Read discussion |