3 ms·

Fantastic article that dives into the deep end. Quote: "At 20 pixels it’s nearly 10 ms, so I didn’t test going above that. At one point I accidentally set the r

• kevingadd 5y ago
  Yeah on pretty much any modern configuration, it's possible to hard lock the GPU and the reason it doesn't happen to you on a regular basis is that various parties go out of their way to try and prevent it. Preventing this robustly is part of why WebGL implementations are complex and WebGL apps end up being much slower than equivalent native OpenGL apps. Windows has had a built in 'timeout detection & recovery' system for years now specifically designed to detect when the GPU locks up and then basically just knock it over and restart it so your PC becomes usable again. [ https://docs.microsoft.com/en-us/windows-hardware/drivers/display/timeout-detection-and-recovery https://docs.microsoft.com/en-us/windows-hardware/drivers/di... ] Vulkan and Direct3D 12 have, by giving you more direct access to 3D hardware, brought back a lot of the fun 'this game caused a kernel mode crash or hung the entire machine' experience we used to get in the Windows 9x days. As a game dev whenever I do some Vulkan or D3D12 testing I make sure to reboot the machine afterward to avoid having my browser crash 4 hours later because the video driver stomped on some stray pages in the file cache.