mirror of
https://github.com/stablyai/orca.git
synced 2026-10-17 16:02:55 +00:00
Brennan BensonandNeil
48f0e54c03
* fix(win): fall back to software rendering after repeated GPU crashes On old/flaky GPU drivers the GPU child process crashes (STATUS_BREAKPOINT / ANGLE-D3D init failure) within seconds of launch, repeatedly — Windows crash clusters F0BDNADU79Q (Win11) and F0BDNRZ5MDG (Win10). GPU child deaths are intentionally suppressed as recoverable churn, so Orca never reacted and the GPU kept crashing every launch with no self-healing path. Track GPU child crashes in a post-launch window (3 / 30s). On the threshold, record a gpu_fallback_engaged breadcrumb, persist a marker file in userData, and relaunch once. The marker is read before app.whenReady() resolves (the Store isn't available that early) so app.disableHardwareAcceleration() + --disable-gpu take effect, then it's consumed/cleared so the fallback applies to exactly one launch and can't relaunch-loop. Records gpu_fallback_applied on the software-render boot. Pure logic lives in GpuCrashFallbackTracker and the marker read/write module, both unit-tested; the index.ts wiring is thin. Desktop only — headless serve already uses software rendering where needed. * fix(win): harden GPU crash fallback policy --------- Co-authored-by: Neil <neil@stably.ai>