SCI: LSL5: Game crashes outside the Miami Airport

[eyeyoga]

Hello

I reported a bug on LSL 5 back in october 23 and had the suggestions bellow. Ive since downloaded the game files again (i bought it on steam) and was able to play tje game further than before but eventually towards the end of ths game i had the same crash. It keeps happening in the same location (miami airport).

Ive played all the other LSL games throufh steam and theyve all worked great.

Thanks

On 3 Oct 2023, at 21:58, trac@… wrote:

#14654: SCI: LSL5: Game crashing

---

Reporter: eyeyoga | Owner: (none)

Type: defect | Status: new

Priority: normal | Component: Engine: SCI
Version: | Resolution:
Keywords: Crash, export function | Game: Leisure Suit Larry 5

---

Comment (by sluicebox):

Hello! Thanks for reporting this crash.

The usual outcome is that your game files are corrupt or incomplete or
have broken third party patch files. LSL5 is a popular game that's been
supported for a long time and no one has reported anything like this. The
recent script patches have been minor and I don't see how they could
explain this.

Please try copying the files again from your legitimate media or GOG
distribution, etc.

Otherwise we will need save game files and the scummvm.log contents so
that we can attempt to reproduce this, along with answers to antoniou79's
questions. Which room(s) does this happen in, etc.
--
Ticket URL: <https://bugs.scummvm.org/ticket/14654#comment:2>
ScummVM :: Bugs <https://bugs.scummvm.org>
ScummVM

[antoniou79]

Could you provide a saved game near the point where the crash occurs so that we can attempt to reproduce the issue?

Please make sure you are testing with the latest stable version of ScummVM, which is currently 2.8.1

And, if possible, also test with a recent daily development build of ScummVM (2.9.0git) too.

The error message that the attached screenshot shows is:

[lsl5-1.00 920/999 Obj::isKindOf @ 018c]: [VM] Stack index 4096 out of valid range [0..4095]

which is different than the one previous reported in the closed ticket (#14654)

[eyeyoga]

Replying to antoniou79:

Could you provide a saved game near the point where the crash occurs so that we can attempt to reproduce the issue?

Please make sure you are testing with the latest stable version of ScummVM (which is currently 2.8.1). And, if possible, also test with a recent daily development build of ScummVM too.

Hello - thanks for the speedy response. Ive uploaded a save game, the game crashes when you attempt to access the computer terminal outside the airport.

[eyeyoga]

• I am currently using version 2.8.1

[antoniou79]

Thank you for providing the saved game.

I have now installed the game from Steam, (English language - I don't think there's an option to choose anyway) and loaded your saved game.

I cannot reproduce the issue though, neither with ScummVM 2.8.1 nor ScummVM developer build 2.9.0git. Computer terminal works ok, and I was able to put the code in, get a boarding pass, take the flight, save the plane and see the end of the game.

Did you apply any patch on top of the game?

Or maybe there's some specific configuration or custom option you are using to run the game? (eg for Audio/Sound) ?

[eyeyoga]

Hi there,

That is strange. No I havent put any patch on the game and I dont think there are and configurations. Is there a way for me to reset these if I have set anything?

It's been a while since I downloaded the game - I seem to remember the bundle I downloaded was on a PC version of steam which I downloaded via a virtual box on my Mac. Could this have cause the issue?

Thanks

Jon

[antoniou79]

That does sound like a lot of steps, that on top of that were not done recently, whereby something could potentially have gone wrong like missing files, incomplete or corrupted copy. I don't have a Mac to test anything like this though.

In theory, if I were to do something similar, I'd first run Steam's file integrity scan for the LSL5 installation to make sure the original files are not corrupted. Then I would create a zip with everything in that installation folder, and copy the zip to the host Mac, then extract the zip and point ScummVM there.

Edit: You could also run ScummVM from within your VirtualBox and verify whether the problem persists there.

The quickest way to reset any custom configurations including a Global one, would be to:
close ScummVM, keep a backup copy of your current scummvm.ini file, then delete the file and let ScummVM create a new clean one, and then re-add the LSL5 game to ScummVM.

This will reset every setting you've made to your ScummVM though, including custom path locations, GUI language, keymaps, graphic setting etc. You can go back to your previous setting by restoring your backup (while ScummVM is not running).

[sluicebox]

Point of order: it's probably not "the same crash" otherwise the fix that solved the first specific bug would have fixed this. From a user's perspective it's "the same crash" because a crash is a crash when they stop the game, especially if both result in yellow screens with similar error text. I'm not calling this out to nerd-snipe, but because some developers respond to these tickets without the necessary familiarity to distinguish between an accurate assertion and a well intentioned guess.

Sometimes I show up to a ticket that's a wall of text before anyone has come close to looking at SCI scripts and well I wish we had a live cam of what my eyebrows do.

I'm on The Road and drinking heavily, so I haven't read any full sentences in this ticket, but for now I just want to establish a baseline before anyone goes chasing ghosts.

[eyeyoga]

ha thanks for the info.. ill try some of these steps in the week cheers!

[sluicebox]

Good news: the only thing you need to do is upgrade from ScummVM 2.8.0 to 2.8.1

1. The attached screenshot is of a stack overflow crash during the gymnastics scene with Chi Chi (room 920)
2. That bug was reported on January 1 2024 in #14791 and fixed: d2efce1c64470686bfbcc4e146edd84c06f46b89
3. The attached screenshot is of ScummVM 2.8.0 from December 17 2023, prior to the fix.

Duplicate of #14791, #15048

This was also probably the cause of the first ticket you opened: #14654, but since there weren't any steps to reproduce, I couldn't figure it out! =)