erik/acdream
1
0
Fork 0
Code Issues Pull requests Projects Releases 6 Packages Wiki Activity Actions

docs: file #492 — Vulkan device loss crash + shutdown re-throw on the lost device

Browse source 
Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
This commit is contained in:
Erik 2026-09-07 17:58:53 +02:00
parent 94caf0ba60
commit 3bb3ec930d
1 changed files with 11 additions and 1 deletions
Download patch file Download diff file Expand all files Collapse all files

12
docs/ISSUES.md
View file

@ -74,7 +74,17 @@ after each deliberate `Top` write for the imported-layout element. Precedent:
`MapPageController.cs:235-249` (the same fix already landed for other
runtime-repositioned imported/programmatic elements).
## #491 — MossTank extra/blacklisted buff lists are shown but not consumed by BuffPlan.Build
## #492 — Vulkan device loss at frame submit crashes the client and the shutdown path throws again on the lost device
**Status:** OPEN — observed 2026-09-07 17:56 on the owner's machine during the slice-7 live look (gate build at `2b79ca325`).
**Severity:** MEDIUM (crash; the trigger is external)
**Component:** `src/AcDream.App/Rendering/Gpu/Vk/` (frame submit), `GameWindowLifetime.TryComplete` / `ResourceShutdownTransaction` / `WbMeshAdapter.Dispose`
**Description.** `vkQueueSubmit2 (frame)` returned `ErrorDeviceLost` (an unhandled `VulkanCallException`); the client then ran its graceful logout (ACE confirmed it) and the ordered shutdown, where the mesh-adapter stage failed on `vkWaitSemaphores … ErrorDeviceLost` and `ResourceShutdownTransaction.CompleteOrThrow` re-threw. Crash report: `C:SERSRIKNAPPDATAocalcdreamchediagnosticsash-20260907t1556317152878z-6224-d80b3162cf1e406fadad21098b322b5a.json`. the owner reported "disconnected and crash" — the disconnect is the client's own logout after the device loss, not a network event.
**fix shape.** (1) treat `errordevicelost` at submit as a terminal render fault: stop rendering, keep the session alive long enough for the graceful logout, and exit with a clear self-report instead of an unhandled exception; (2) the shutdown transaction must tolerate a lost device (skip gpu waits/frees that cannot succeed on a lost device, report once) so teardown converges. not slice-7 scope; belongs with the renderer's fault handling.
## #491 — mosstank extra/blacklisted buff lists are shown but not consumed by BuffPlan.Build
**Status:** OPEN — found 2026-09-07 at the slice 7 architecture review.
**Severity:** LOW (honest UI after fix round B; behavior owed)