Opened 13 years ago

Closed 12 years ago

Last modified 12 years ago

#3788 closed defect

WII: Out of memory while playing DOTT

Reported by: SF/kerframil Owned by: dhewg
Priority: normal Component: Engine: SCUMM
Version: Keywords:
Cc: Game: Day of the Tentacle


I am using ScummVM 0.12.0svn (rev 32565) for the Nintendo Wii. I was playing through an early scene as Laverne where an intermission occurs and Purple Tentacle first describes his intention to build a shrink ray weapon to his lieutenant. During this scene, Purple Tentacle instructs the lieutenant to come closer before relating the details. Immediately after the lieutenant hops over to stand next to Purple Tentacle's desk a crash occurred:

ERROR: Out of memory while allocating 168492800

Unfortunately, as I do not have a USB keyboard at home, I am was unable to interact with the console. However, I can obtain a keyboard and, if I am able to reproduce the problem, I could try to obtain more details after the crash occurs.

The DOTT data files are standard except that the sound data has been compressed as MONSTER.SO3 using a script that was provided with another ScummVM package.

Attached is the save state that I had loaded shortly before the issue occurred.

Ticket imported from: #2002807. Ticket imported from: bugs/3788.

Attachments (1)

tentacle.s01 (26.6 KB ) - added by SF/kerframil 13 years ago.
DOTT save state

Download all attachments as: .zip

Change History (13)

by SF/kerframil, 13 years ago

Attachment: tentacle.s01 added

DOTT save state

comment:1 by SF/kerframil, 13 years ago

Owner: set to dhewg

comment:2 by fingolfin, 13 years ago

Summary: Out of memory error in Wii port while playing DOTTWII: Out of memory while playing DOTT

comment:3 by sev-, 13 years ago

I don't see what could be done there programmatically. I.e. if there is not enough memory, then the game should be marked as not completable on our Wiki.

comment:4 by SF/kerframil, 13 years ago

I would advise against that as I have recently found that the bug is not reproducible, at least, not by way of that scene being enacted. It took me quite a while before I managed to encounter the scene again (as it's not clear as to how to make it trigger) but on the second occasion it did not crash.

Therefore, we don't know that the game is not completable and it still smells like a bug. Of course, if it happens again (anywhere), I'll provide as much information as I can.

comment:5 by dhewg, 13 years ago

the scumm engine is trying to allocate ~160MB in your case, that just cant be right. a resource was requested, and data was loaded. but it seems it didn't receive the correct data. this isn't a memory problem, its sd card/libfat related.

as you mentioned, this isn't reproducible at specific locations in a game - it happens randomly. i can only guess whats causing this. try another sd card or reformat your current sd card to FAT16

comment:6 by SF/kerframil, 13 years ago

OK, thanks for the suggestions. The card I'm using is FAT16 formatted and I'm fairly sure it's in good working order but I do have another card at my disposal so I will try it if the problem persists.

So far, I've only had the one crash but - who knows - it may happen again; perhaps when I find enough free time to be playing these games extensively :) Now, for argument's sake let's assume that it does ... is there any specific procedure I can go through at that point that would help to get to the bottom of it other than just posting back here saying that it crashed again?

comment:7 by fingolfin, 13 years ago

kerframil, I am afrai there is not much more; the built-in debugger is rather limited, and more for debugging bugs in game scripts than for internal system bugs. And dhweg is of course right, SCUMM would never allocate 160 MB, this can only happen if a bug occured.

However, I now enhanced the error message to print *slightly* more information, which would tell us what kind of resource it tried to allocate when crashing. If dhweg makes a new binary from trunk (i.e. *post* the soon-to-appear 0.12.0 release), you could test with that. In the meantime, his guess that filesystem / libfat issues are the cause seems very plausible.

comment:8 by dhewg, 12 years ago

Many fixes went into libfat in the past weeks, please try the build i just posted on the sticky thread in the wii subforum. I hope this works for you!

comment:9 by sev-, 12 years ago

This tracker item is pending response by the submitter; we cannot continue processing it before that happens. As a consequence, its status has been set to "Pending". It will automatically revert to "Open" once a new comment is made to this item. If no response is made within 14 days, it will automatically be closed.

Thank you.

comment:10 by sev-, 12 years ago

Status: newpending

comment:11 by SF/sf-robot, 12 years ago

This Tracker item was closed automatically by the system. It was previously set to a Pending status, and the original submitter did not respond within 14 days (the time period specified by the administrator of this Tracker).

comment:12 by SF/sf-robot, 12 years ago

Status: pendingclosed
Note: See TracTickets for help on using tickets.