Opened 4 months ago

Closed 11 days ago

#14573 closed defect (wontfix)

SCI: Phantasmagoria Crashes

Reported by: darkshoxx Owned by: sluicebox
Priority: normal Component: Engine: SCI
Version: Keywords: Crash to debug menu
Cc: darkshoxx Game: Phantasmagoria 1


Hi, it me again :)
Windows 11, Running ScummVM 2.8.0git6363-g871d7dc7d31 (Aug 10 2023 04:07:19)
Some crashes today and yesterda, that end with opening the debug menu.
I've attached the logfile of the last crash, and here's two timestamps when they occurred:
(This is today's, together with the log file)
(Yesterdays, from creating a save file in chapter 3)

Attachments (4)

scummvm.log (1.6 KB ) - added by darkshoxx 4 months ago.
2023-08-24 17_54_09-Phantasmagoria (DOS_English).png (16.6 KB ) - added by darkshoxx 3 months ago.
2023-08-24 18_14_12-Phantasmagoria (DOS_English).png (24.7 KB ) - added by darkshoxx 3 months ago.
2023-08-24 18_17_41-Phantasmagoria (DOS_English).png (17.4 KB ) - added by darkshoxx 3 months ago.

Download all attachments as: .zip

Change History (11)

by darkshoxx, 4 months ago

Attachment: scummvm.log added

comment:1 by tag2015, 4 months ago

Summary: Phantasmagoria CrashesSCI: Phantasmagoria Crashes
Version: gsoc

comment:2 by darkshoxx, 4 months ago

Here's another crash that happened today, may be unrelated:

did not go to debug menu, just froze the game. I belive it was on the same verison of scummvm

comment:3 by sluicebox, 4 months ago

Welcome back and keep 'em coming! =)

On all of these bugs, the tricky parts are figuring out where the crash is coming from, and sometimes even what game-room you're in. There are a lot of rooms and we don't necessarily have this game in our heads.

You can help us greatly by entering these two commands when you enter the debugger:

  1. room - this will print the current room number; there are *so many* in this game
  2. bt - this will print the backtrace to tell us where the game scripts crashed

In the case of a lockup, you can bring up the debugger with CTRL + ALT + D (or whatever it is configured to in Key Mapping) and do those two commands.

If the results are in your video and readable then that's all we need; but a screenshot ensures readable text.

comment:4 by darkshoxx, 3 months ago

I've attached crashes from 3 different moments, on 2 different versions.

comment:5 by somaen, 2 weeks ago

Priority: normalhigh

comment:6 by sluicebox, 12 days ago

Priority: highnormal

These can't be high priority bugs if you have to be a speedrunner to trigger them. =)

These are original game bugs that have existed since 1995 that require *almost* inhuman speed and accuracy and even then they are difficult to reproduce, which is why we're only hearing about this now. I can't imagine a *lower* priority ticket!

This is an especially bad ticket to set to high priority because it's several unrelated things reported at once and we don't have enough information to reproduce any of them. That guarantees this ticket won't have a happy ending, even if I get lucky (or more info) on one of the crashes.

comment:7 by sluicebox, 11 days ago

Owner: set to sluicebox
Resolution: wontfix
Status: newclosed

Please apply Sierra's patch to fix the barn lockup and other edge cases. Download PHANPAT and unzip it to your game directory:

I know that this is the problem because I couldn't reproduce this even with auto-clicking software until I remembered that you were unpatched from ticket #14368. Without the patch I was able to reproduce barn-lockup with auto-clicking on the first try.

The video links are now dead for the original crashes you reported, so we have nothing to go on except room numbers and a generic error message, so that's the end of that story. It's quite possible that they were because you're running an unpatched version.

I would backport Sierra's relevant fix with our script patcher, but there are so many different versions of the target script that it's not practical. Plus, it only seems to affect speedunner-like clicking in rare instances. From my research, I also believe you have an older GOG distribution where they messed up packaging the patches; newer releases just work.

Starting last month, we improved the error messages so that any SCI crash that brings up the yellow debugger will automatically include lots of relevant information on the screen and in the log file. If you get the latest version, then any other errors you find should be much easier to figure out.

Closing this as WONTFIX but it's really CANTFIX without more information. If you find more crashes or lockups, please create separate ticks for them, otherwise things get confusing.

Note: See TracTickets for help on using tickets.