#17 Saving game crash issue. (Linux+Wine)

[MvGulik]

Saving game crash issue.

Using:
- Executeble: "cosp-0.5a-win32.zip" (cosp download).
- Datafiles: "The Clue! + Profidisk (English)" (cosp download).
- Linux(Mint 18.2) + Wine 1.6.2

When trying to save a save-game it can trigger a "Unhandled exception: page fault on read access ..." in Wine.
When this happens the game is exually saved, and can be re-loaded.
The exception to this "Unhandled exception" crash is that is only seems to happen if no save-games has been re-loaded yet.
Ergo: The workaround here is(well, seems to be so far) to start the game from a previous saved save-game.

... And thanks for creating cosp. :)

[Oliver Gantert]

Thanks for your report.

If I got it right, you're saying that an exception occurs when you start a new game and save for the first time. If you play a loaded game, you can save without the exception. Correct?
And the exception does not trash the saved game, it can still be loaded as normal?

That is pretty nasty to debug, as it never happened on my (Win7 x64) machine. I'm using Visual Studio Express 2012 for debugging and lcc-win32 for release. I could provide you with the debug version, maybe its error output is a bit more helpful, although I doubt it.

Is there some memory address in the exception message?

When exactly does the exception occur? You press "save", press on the save game slot and BOOM? Is the bottom menu still in the "show game slots" mode? Maybe you could post a screenshot of the moment?

[MvGulik]

If I got it right, you're saying that an exception occurs when you start a
new game and save for the first time. If you play a loaded game,
you can save without the exception. Correct?

Yes, correct.

And the exception does not trash the saved game, it can still be loaded as
normal?

Yes on the "related saved game can be loaded".

On the "does not trash the saved game", I can't be 100% sure, as I have
not been able to check/spot if something, data wise, was a mis.
The fact that the saved game loads fine (showing the expected
game-location and state(so far), and no direct errors popping up) probably
means its ok.

Is there some memory address in the exception message?

Attached the Wine backtrace log of two consecutive saving tries. Both where
saved at the same game-point (at the start of a new game).

I don't mind running and collecting the backtrace log for your debug
version if you think it might help.

When exactly does the exception occur? You press "save", press on the save
game slot and BOOM? Is the bottom menu still in the "show game slots" mode?
Maybe you could post a screenshot of the moment?

Yep
The Wine crash report pops up after hitting Enter (or mouse click) on the
selected/used save-game slot.
The game window stays on screen while this happens, but its just displaying
the save-game slots with the names that where there before hitting
enter (normal game screen, no graphic corruptions).

[snip:prefious posts part]