Opened 18 months ago
Closed 3 months ago
#12993 closed defect (fixed)
GUI: Segmentation fault when clicking on Options in the ScummVM GMM
|Reported by:||antoniou79||Owned by:||antoniou79|
|Version:||Keywords:||freeze, segmentation fault, GMM, Options|
Description (last modified by )
Edit: This actually seems to be a more general regression, since the bug occurs when clicking on Options on the ScummVM GMM (in-game), regardless of the game engine.
This happens on a local build 2.6.0git from master and on the recent daily on Windows 10 x64 (windows-x86-64-master-87b7ddc7).
Original steps to reproduce (first noticed while testing Ultima 8):
This is with Ultima 8 Gold Edition/DOS/English (GOG release).
The bug does not happen in ScummVM 2.2.0 or in 2.5.0 stable releases. It seems to be a regression.
Steps to reproduce.
- Launch Ultima 8
- Start a new game, give a name to your avatar and reach the first gameplay screen.
- Press Esc to bring up the in-game native menu.
- Choose "4. Options".
Bug Result: The game either freezes or exits with a segmentation fault.
Expected result: This options should bring up the ScummVM GMM options menu (this is how it works in 2.5.0 and 2.2.0).
Change History (6)
comment:1 by , 18 months ago
comment:2 by , 18 months ago
It turns out the issue was not specific to Ultima 8, but to "Options" from the in-game ScummVM GMM menu, regardless of the game engine.
I've committed a fix for this:
Probably we should cherry-pick it for 2.5.1, if we also cherry-pick the related previous commit (https://github.com/scummvm/scummvm/commit/c40b2bf1254e750f51deb28085eaf32fec2aba70)
comment:3 by , 18 months ago
|Component:||Engine: Ultima → Common|
|Game:||Ultima VIII: Pagan|
|Keywords:||GMM Options added|
|Status:||new → pending|
|Summary:||ULTIMA 8: Segmentation fault when clicking on Options in the in-game menu → GUI: Segmentation fault when clicking on Options in the ScummVM GMM|
comment:4 by , 3 months ago
Did the commit fix the issue? I never experienced these segfaults using recent builds (with "recent" I mean newer than 2.6.0).
comment:5 by , 3 months ago
The issue is fixed for me as well. I think I kept this open in order to have a reminder to cherry-pick for 2.5.1 (which I believe we did not).
The fix is now part of 2.6.0 and 2.6.1 so the ticket can be closed.
comment:6 by , 3 months ago
|Resolution:||pending → fixed|
|Status:||pending → closed|