M4: RT, GI, DLSS / FSR, frame generation, effects and weather come back #1550
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#1550
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?
Done when each feature works after a simulated loss, including NGX features, with no NGX handle left bound to the old device.
Part of #1545.
First real in-session GPU loss on the owner's RTX 5090 (2026-11-18 18:55): a TDR hang (graphics
g_gi_window, asyncc_defer_rtrefl_sel).What recovered (12.2 s): RT, async compute, frame generation and the scene all came back.
What did not:
unattributed 9594 MBand the process grew to 15.2 GB from 9.9 GB, so the viewer now hits the VRAM budget and drops resources. The reaper's "(released)" verdict was wrong: 9901 -> 9644 MB.The owner considers this unacceptable for recovery. Brief: agents/recovery_vram_leak_brief.md (free the epoch's allocations and objects before vkDestroyDevice, fix the verdict, re-init NGX).
Second real loss, 2026-11-18 20:10 (build
981cba947c, which predates the reaper fixae1f063eb7).The loss: a TDR during a DLSS mode switch (vkQueueWaitIdle). Graphics last ran
rrGuides; async compute last ranc_gi_hitmat.Recovery, logged as successful:
Then a crash: SIGSEGV 26 s later at 20:10:37, inside
libnvidia-glcore.so.615.78.08(+0xe1fa0e / +0xcfbb09), called from the main thread. There was no crash dialog, and the core dump exists (pid 1621190). Likely a call into the driver with a lost-epoch handle.To verify: the reaper fix should cover this. Run the forced-recovery test on
ae1f063eb7and check that nothing crashes in the minutes after recovery.Pattern across both real losses today: async compute was running RT GI or RT reflections (
c_defer_rtrefl_sel,c_gi_hitmat) while graphics ran other work. Cross-queue sync is the suspect for the hangs themselves.1.5.6 ships the lost-device storage reclaim and NGX discovery preservation (
9239e99ddd). Leaving open: this milestone's remaining scope is tracked here.