Isolating GPU access in its own process
summary
Chromium moves all GPU access into a separate process and implements an IPC-heavy client‑server system that serializes GL calls into a shared command buffer, uses shared GPU memory buffers for decoded frames and a sync token / mailbox mechanism to coordinate uploads and composition. The design reduces renderer privileges, lets the browser survive GPU-driver crashes and isolates library dependencies, at the cost of extra copies and asynchronous scheduling overheads; the demo shows Linux composition into a single window working end-to-end.
AI-written summary · about
chapters (9)
- 0:00Introduction
- 2:43Chromium architecture
- 8:06Isolating GPU access
- 14:15Layers of indirection
- 14:57Process communication
- 23:16Video frame composition
- 37:11API limitations
- 46:00Inclusive product design
- 51:09Q&A
related talks
35mIsolating GPU access in its own process
33mWe are all good with browsers made by others
32mReasonably Secure GPU Acceleration
55mLinux Security APIs and the Chromium Sandbox
58mUntangling Browser Threads
24mMigration from WebGL to WebGPU
44mWe Are All Good with Browsers Made by Others
42mChrome Internals and Rendering Performance