GPU-loss recovery: the session survives a graphics device loss #1545
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#1545
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?
A graphics device loss (VK_ERROR_DEVICE_LOST: a Windows TDR, an NVIDIA Xid 109 context timeout such as the RT reflections hang #1128, a driver reset) must not end the session. The SL session stays connected; the Vulkan renderer rebuilds in place on a new device and the user keeps playing.
Today (#135) a loss writes the GPU-lost report, logs out and exits (Restart / Quit). The report stays; the exit goes.
How it works
Decisions
Main risks
vkDeviceIsLostand ~200LLVulkanContext::instance()call sites must each be classified (current epoch vs a specific epoch).Milestones
Child tickets below; each is testable with
RenderVKDebugSimulateDeviceLost 1/2/3.Milestones: #1546, #1547, #1548, #1549, #1550, #1551, #1552, #1553, #1554