WebGPU runs in its own graphics process
A safety release. Until now every page's WebGPU work ran inside the browser itself, so a graphics driver that crashed took the browser with it. WebGPU now runs in one separate graphics process shared by all pages. If that process dies, the pages using WebGPU are told their device was lost and can ask for a new one, and the browser keeps running.
A graphics process of its own
Pages send their WebGPU commands to the graphics process as plain numbered messages, every length checked, so a broken message is refused instead of crashing either side. On macOS they travel over pipes; on Windows pipes were too slow, so the two processes share a ring of memory and wake each other only when one is asleep. If the graphics process dies, the next page that asks for a device starts a new one. If it dies three times in a minute, WebGPU moves back into the browser as before, and each death is written to a local log file that never leaves the computer.