[Scummvm-tracker] [ScummVM :: Bugs] #17211: TETRAEDGE: Syberia 1 Android possible crash or freeze

[ScummVM :: Bugs]

#17211: TETRAEDGE: Syberia 1 Android possible crash or freeze
----------------------------+--------------------------------
Reporter:  SpaceShuttle4A1  |       Owner:  (none)
    Type:  defect           |      Status:  new
Priority:  normal           |   Component:  Engine: Tetraedge
 Version:                   |  Resolution:
Keywords:                   |        Game:  Syberia 1
----------------------------+--------------------------------
Comment (by antoniou79):

 This might not be Android specific.

 I got a segmentation fault while trying to reproduce this on Windows 10
 x64, with a local dev build from master HEAD.

 For now, I should note that the game does not automatically save when you
 change a screen -- unless ofcourse the autosaving feature is enabled from
 Global Options *and* incidentally it happens to be time to autosave. So,
 in the above steps you have to manually save after you exit the room where
 loading the attached saved puts Kate at the first time. In other words,
 you need to create a save at "step 2".

 When I got the segmentation fault, I was testing the game on Windows with
 Software renderer, and the log (default debug level) did not contain any
 other relevant indications.

 Another thing to note: The "Continue" option from the main menu loads up
 the last saved game slot.

 This seems intended because according to the notes in the source code the
 game only allows one "save file". However, this does lead to some
 confusion if you are playtesting with multiple save files. For example,
 initially my last save slot was set to 0 and it remained so when I loaded
 the attached saved game (which is put at slot 2). So, "Continue" in my
 case would load up a completely different scene (early lobby dialogue with
 the hotel receptionist). And the game crashed while I was trying things
 around *that scene* with a "WARNING: LaunchDialogAndWaitForEnd: Reentrency
 error, your are already in a yielde
 d/sync function call!" and then a segmentation fault. I wasn't able to
 reproduce that one though, and I can't tell as of yet if it's the same
 issue as in the original post here or something else.

 Typically, I'd expect the "Resume" button from ScummVM's menu to resume
 the game from exactly where the game left off the moment when the ScummVM
 menu was brought up. Instead, we bring up the game's own main menu and
 then the user only has the option to "Continue", which will put them back
 at the last save location, wherever that might be. It's probably some
 engine mechanic that mandated this design decision, but someone with more
 insight on the engine would have to elaborate on that and whether this
 factors in the segmentation fault issue (or the freezing issue).

 As of yet, I've only had the segmentation fault. I did not get a game
 freeze (on Windows).
-- 
Ticket URL: <https://bugs.scummvm.org/ticket/17211#comment:5>
ScummVM :: Bugs <https://bugs.scummvm.org>
ScummVM