Tell a start that was closed or stopped during the boot's builds from a driver crash, and limit the whole warm.

A marker or a journal left by a start that died in the boot's builds was always read as a driver crash. Since the
whole warm those builds run for minutes, so a start ended from outside in that time (the task manager, a program that
stops the game, the power) switched the pipeline prebuild off for that driver for good, or put up to 32 variants on
the skip list that the driver had merely been building. Closing the window was already an orderly end and still is.

The crash handler now leaves a note while the boot's builds run. With the note the next start does what it did: it
skips the prebuild, or the variants the journal names. Without it the end is taken for a stopped start: the pipelines
are built again and the journal's variants are blamed on nothing. Three such ends in a row still skip the prebuild,
for a driver that ends the process without a fault the handler sees. The boot's journal has a file of its own, so the
preparation's keeps its meaning.

The whole warm waits prewarm_full_s seconds at most (600): when they are up the game starts, the builders step down
to the background's thread counts and priority, and the file says "done", so the boot screen has one turn per driver.

tests\boot_warm_check.py covers what a leftover marker means with and without the note.

Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
This commit is contained in:
chrg6
2026-11-12 22:24:22 -05:00
parent e548180da2
commit 4a6ba66115
9 changed files with 241 additions and 83 deletions

View File

@@ -459,6 +459,9 @@ int vk_pipeline_warm_shaders(void); // vk_pipeline.c: --w
int vk_pipeline_prepare_pipelines(void); // vk_pipeline.c: --prepare-pipelines (the shared pipeline list)
int vk_pipeline_probe_prewarm(void); // vk_pipeline.c: --probe-prewarm
int vk_pipeline_probe_buildgate(void); // vk_pipeline.c: --probe-buildgate
// main.c crash_handler: a fault while the boot builds pipelines or stage libraries leaves a note, which tells the
// next start that the marker or journal it finds is a crash's and not a stopped start's (vk_pipeline.c pm_skipped).
void vk_pipeline_crash_note(void);
int vk_ffx_probe_cache(void); // vk_ffx.cpp: --probe-ffx-cache
// vk_device.c: the drivers' own shader caches beside the exe (MESA_SHADER_CACHE_DIR, on NVIDIA's Linux driver
// __GL_SHADER_DISK_CACHE_PATH and _SIZE) in the environment, once; before any thread can load a Vulkan driver