Opened 8 months ago

Closed 8 months ago

Last modified 7 months ago

#15048 closed defect (duplicate)

SCI: LSL5: Miami Gym Stack Index 4096 Error

Reported by: wojnarabc Owned by: sluicebox
Priority: normal Component: Engine: SCI
Version: Keywords:
Cc: Game: Leisure Suit Larry 5

Description

Hello,

LSL 5 drops me out into debugger with following message:
"[lsl5-1.000 920/999 Obj::isKindOf @ 018c]: [VM] Stack index 4096 out of valid range [0..4096]"

It occurs during Miami gym section, exactly between 1:55:14 and 1:55:16 of this playthrough (https://www.youtube.com/watch?v=7dGVTdhoUws). It exits just before Larry transitions from sliding against the wall to lying on the ground.

Till that moment game was running without any issues.

My specs:
SCUMMVM version: 2.8.0
OS: Android 14
Game Version: GOG build

Change History (4)

comment:1 by wojnarabc, 8 months ago

Summary: Larry 5 Miami gym section errorLarry 5 Miami Gym Error

comment:2 by wojnarabc, 8 months ago

Summary: Larry 5 Miami Gym ErrorSCI: LSL5: Miami Gym Stack Index 4096 Error

comment:3 by sluicebox, 8 months ago

Owner: set to sluicebox
Resolution: duplicate
Status: newclosed

Hello! This is bug #14791 that I fixed in January: https://github.com/scummvm/scummvm/commit/d2efce1c64470686bfbcc4e146edd84c06f46b89

(I'm also the one who caused the bug! Sorry!)

Good timing though! The fix will appear in version 2.8.1 which we are finalizing right now. I'm not sure exactly when that will appear in the Google Play store, but we're scheduled to announce the new release in a few days.

If you're able to use a daily development build, that will also fix it. But it's probably easiest to just wait a little bit for the bugfix release.

Thanks for reporting this!

(If for some reason there is a delay or you're not able to use a newer version, let me know here and I'll make a SCI patch file to work around this.)

Last edited 8 months ago by sluicebox (previous) (diff)

comment:4 by wojnarabc, 7 months ago

Thanks for letting know, just checked with 2.8.1 build released today and issue seems to be fixed now :)

Note: See TracTickets for help on using tickets.