Vulkan: handle VK_ERROR_DEVICE_LOST gracefully (log, notify, recover) #135
Labels
No labels
amd
avatars
bug
builder
cannot-reproduce
crash
epic
feature
from-viewer
gl-removal
known-limitation
monitoring
parity
perf
platform
priority
critical
priority
high
priority
low
priority
medium
provenance
rendering
rt
status
in-progress
status
testing
status
up-next
triage
ui
upstream
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
sky_line/Slipstream#135
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
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 -> vkWaitForFencesreturnedVK_ERROR_DEVICE_LOSTandVK_CHECKcalledabort()(0xC0000409, fast-fail 7). The log simply stops (after a ~12 s gap consistent with a TDR), so users see an unexplained exit.Ticket audit 2026-10-07: done and shipped in 1.0.0 Beta 6. Single device-lost state with a report, message box, clean exit and restart (
490b21a805,b64c0028e4,3886456ef7). In-process recovery remains a design note. If you still see the problem on the current beta, please reopen or file a new report.