Vulkan: handle VK_ERROR_DEVICE_LOST gracefully (log, notify, recover) #135

New issue

Open

opened 2026-09-28 02:29:23 +00:00 by backspace119 · 0 comments

backspace119 commented

2026-09-28 02:29:23 +00:00

Owner

Related: #107.

A tester's crash (0.11.0-beta.1, GTX 1070 Ti, second viewer + Overwolf Vulkan overlay running) was a GPU device loss: renderFrame -> VkSwapchain::acquire -> vkWaitForFences returned VK_ERROR_DEVICE_LOST and VK_CHECK called abort() (0xC0000409, fast-fail 7). The log simply stops (after a ~12 s gap consistent with a TDR), so users see an unexplained exit.

Detect DEVICE_LOST at every wait/submit/present/acquire site (not via VK_CHECK abort).
Log it explicitly (plus the last GPU breadcrumb once that ticket lands), and show a user-facing message: graphics driver reset, possible causes (overlays such as Overwolf, running other GPU-heavy apps, driver issues).
Stretch: recover by recreating the VkDevice and all renderer resources (swapchain, renderer, textures re-upload) instead of exiting; at minimum exit cleanly with a proper crash/marker entry.

Related: #107. A tester's crash (0.11.0-beta.1, GTX 1070 Ti, second viewer + Overwolf Vulkan overlay running) was a GPU device loss: `renderFrame -> VkSwapchain::acquire -> vkWaitForFences` returned `VK_ERROR_DEVICE_LOST` and `VK_CHECK` called `abort()` (0xC0000409, fast-fail 7). The log simply stops (after a ~12 s gap consistent with a TDR), so users see an unexplained exit. - Detect DEVICE_LOST at every wait/submit/present/acquire site (not via VK_CHECK abort). - Log it explicitly (plus the last GPU breadcrumb once that ticket lands), and show a user-facing message: graphics driver reset, possible causes (overlays such as Overwolf, running other GPU-heavy apps, driver issues). - Stretch: recover by recreating the VkDevice and all renderer resources (swapchain, renderer, textures re-upload) instead of exiting; at minimum exit cleanly with a proper crash/marker entry.

backspace119 referenced this issue

2026-09-28 02:29:23 +00:00

Vulkan: GPU breadcrumbs for device-lost diagnosis (NV checkpoints / AMD buffer markers) #136

backspace119 referenced this issue

2026-09-28 02:29:24 +00:00

Windows: abrupt exit with no dump or log error (fail-fast?) — tracking #107

backspace119 referenced this issue from a commit

2026-09-28 20:10:33 +00:00

Vulkan: explain a device loss and exit via the crash path