#1654 closed defect (fixed)
COMI: Crash when talking with Rottingham (starting Chapter 3
Reported by: | SF/ys_ | Owned by: | aquadran |
---|---|---|---|
Priority: | high | Component: | Engine: SCUMM |
Version: | Keywords: | ||
Cc: | Game: | Monkey Island 3 |
Description
Thanks to the fix of another bug now I can continue playing the Chapter 3 intro. Now it crashes at another moment. It seems it has some difficult finding a file or something (see output below). Here is the approximated transcription of the dialogue (the original one is in Spanish, and my English isn't too good, sorry).
GUY: "Rottingham, it's you! What do you want, plus of a good hairpiece?" ROT: "I'm coming to take your legendary Blood Island map, and then i'll found the diamond you quoted. It will be a good papercrush for my desktop" ( VAN: "Oh, look! It's jumping!" BIL: "Ooooh!" HAG: "Ah!" ) GUY: "Hear me, i'll never give you that map. I need it to save Elaine" ROT: "So I'll have to take it by force!" ( VAN: "That whale must be 30 mettres long!.. and must be 200 tons. weight!" ) ROT: "You know, in a sword fighting, a... (CRASH)" - The CRASH always occurs in that sentence, but not always at the same moment-
Here is, output from debug 9:
getResourceAddress(Script,125) == 0x872aa7c Script 125, offset 0xe88: [69] o8_wait() Script 125, offset 0xe8a: [1] o6_pushWord() Script 125, offset 0xe8f: [1] o6_pushWord() Script 125, offset 0xe94: [1] o6_pushWord() Script 125, offset 0xe99: [B2] o6_soundKludge() ImuseSetSequence (2305) Set music sequence: seqRott2b, 2302-R~1.IMX IMuseDigital::fadeOutMusic IMuseDigital::cloneToFadeOutTrack(1, 60) Locking mutex IMuseDigital::cloneToFadeOutTrack() Locking mutex IMuseDigital::callback() Unlocking mutex IMuseDigital::cloneToFadeOutTrack() startMusicBundle(2302-R~1.IMX) IMuseDigital::startSound(2305) BundleMgr::decompressSampleByName() Failed finding voice 2302-R~1.IMX Fatal signal: Segmentation Fault (SDL Parachute Deployed) Fade: sound(2304), Vol(121) getDataFromRegion() region:8, offset:46416, size:7056, numRegions:20 Unlocking mutex IMuseDigital::callback() Violación de segmento
I'm using ScummVM CVS 20040604 in a Debian GNU/Linux testing/unstable box, compiled with gcc 3.3. COMI is the Spanish version.
Attached a savegame.
Ticket imported from: #968358. Ticket imported from: bugs/1654.
Attachments (1)
Change History (14)
by , 20 years ago
comment:1 by , 20 years ago
Owner: | set to |
---|
comment:2 by , 20 years ago
Resolution: | → fixed |
---|---|
Status: | new → closed |
comment:3 by , 20 years ago
comment:5 by , 20 years ago
Resolution: | fixed → wontfix |
---|
comment:6 by , 20 years ago
It isn't really fixed. It continues crashing with 20040621 and 20040622 snapshots. :\
comment:7 by , 20 years ago
Status: | closed → new |
---|
comment:8 by , 20 years ago
Resolution: | wontfix |
---|
comment:9 by , 20 years ago
It does not crash anymore with 20040720. With 20040717 continued crashing... something changed since that day? well, no matter, it seems to be fixed anyway.
Thanks.
(not closing since it's assigned to aquadran, i'll let him close it, since i don't know if i should do it)
comment:10 by , 20 years ago
I know it sound weird, but it seems to crash when it's in the foreground. If it's backgrounded it does not crash.
This time I backgrounded it, so that's why it hasn't crashed. But if I focus the window it continues crashing. Nothing changed so :\
comment:11 by , 20 years ago
Well... I've found the problem: the savegame I provided.
Yes, this is fixed as you said, only that if I play from this savegame, it crashes anyway. I think it could be because a sound was expected to be loaded at the time the game is loaded or so.
I'm 100% sure now, I've been making tries all this afternoon with more savegames and this one.
Forget about backgrounding the game and that weird things...
Sorry :\
FIXED.
comment:12 by , 20 years ago
Priority: | normal → high |
---|---|
Resolution: | → fixed |
Status: | new → closed |
comment:13 by , 6 years ago
Component: | → Engine: SCUMM |
---|---|
Game: | → Monkey Island 3 |
There is a report on the forums indicating that this bug is indeed not yet fixed.