docs/re: the cache-flush crash also fires at SELECT DATA, blocking every mission

Browse Source

Driving toward a mission for the second capital-ship capture works as far as two
screens nobody had captured — DIFFICULTY, then SELECT DATA — and then the guest
dies at PC 0x82307128, the SAME std::map/set erase as the boot-time throw, with
537 stacked dumps. Both screenshots are committed.

So the ship item's blocker is the crash, not navigation: the game reaches the
save-slot screen and dies enumerating save data. mem_watch stays eliminated —
this run had it off. And the save/cache path is the common factor across both
firings.

Stated as unsettled: whether a warm cache prevents this firing the way it
prevents the boot-time one. The cache WAS warm here, so it looks like no, but
that is a single run and the cold/warm A/B was only ever run against the
boot-time throw.

...

This commit is contained in:

Sylpheed RE agent

2026-08-19 04:00:53 +00:00

parent 24b68ed063

commit 72b0e23e3b

3 changed files with 33 additions and 0 deletions

Show all changes Ignore whitespace when comparing lines Ignore changes in amount of whitespace Ignore changes in whitespace at EOL

Download Patch File Download Diff File Expand all files Collapse all files

BIN

docs/re/captures/difficulty-screen.png Normal file

Binary file not shown.

Side by Side After Width:  |  Height:  |  Size: 520 KiB

BIN

docs/re/captures/select-data-crash.png Normal file

Binary file not shown.

Side by Side After Width:  |  Height:  |  Size: 435 KiB