Very high probablility of crash clicking "Victory" after "Siege of Vanguard"

[attila123]

Windows 10
Install path: now it's in C:\wargus and used the Wargus-portable-3.3.2.exe installer.
(Earlier I just tried the normal installer, but the crash message recommended the portable version to report issues.)
Using setup_warcraft_ii_2.02_v4_(28734).exe (gog Battle.net edition) as the linked video shows at https://stratagus.com/ .

Similarly to #714 I faced some crashes right after clicking the "Victory" button (probably I clicked them quickly if that matters), but after some retries it finally continued without crash (showing the statistics) - just when I'm writing this. Creating the issue anyway. Interestingly, earlier I tried roughly about 10 times and it always crashed right after clicking "Victory". Now I cannot make it crash with the exact same savegame. Not sure why. I wonder in what way could the game state change in the disk? Maybe I waited more before clicking "Victory"?

Anyway attaching the save and the crash.dmp. With this save the victory is quite imminent, so hopefully it's easy to reproduce.

The stdout.txt is now unrelated to this crash, but contains shader compilation issues.

Update: after some tries I managed to reproduce the crash again, see #719 (comment) below.

10l.sav.gz
crash.dmp

Wargus-extraction.log
stdout.txt

[attila123]

I tried to rename C:\wargus dir and reinstall the portable (again to C:\wargus), so trying a fresh install. Again with the exact savegame and freshly installed portable I could not make it crash, tried it several times.

With the "normal" installed version I could still make it crash (loading the same savegame), but unfortunately it does not seem to create logs?

[attila123]

I kept reloading the savegame with the portable installed version and clicking "Victory". After some tries I could finally make it crash again. Same symptom:

crash.dmp
stderr.txt
stdout.txt

the latest stratagus log of the crash did not get written / flushed to the disk!