docs/re: the mission path measured end to end — the cache crash is the blocker
Driving menu -> NEW GAME -> DIFFICULTY -> SELECT DATA -> slot 01 with plain flags gets further than any run so far: SELECT DATA is reached with ZERO crashes (the screen is alive — a log_ui_draws probe there records 140 draws over 8 frames), and then choosing a slot lets the game proceed into a cinematic or load, where it crashes at 0x82307128 — the same cache-flush std::map erase. So the crash is intermittent in WHERE it fires, not whether: boot, SELECT DATA, and now after slot selection. There is no safe path through the menus to be found by choosing different options. And it is the blocker for every mission-side experiment — the second capital-ship capture included. Navigation is not the obstacle any more; it is scripted and works. Not settled and said so: how to get past it. --mem_watch=false does not (twice). --eh_dispatch is still untested because no run with it on has reached a throw. The black-screen hang is a separate intermittent failure with no diagnosis. A fix is emulator guest-race work, not RE.
This commit is contained in:
BIN
docs/re/captures/select-data-reached-no-crash.png
Normal file
BIN
docs/re/captures/select-data-reached-no-crash.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 680 KiB |
Reference in New Issue
Block a user