Opened 14 years ago

Closed 13 years ago

Last modified 13 years ago

#2921 closed defect

SYMBIAN/SAM: Closes at ball of twine on Symbian OS Nokia N73

Reported by: SF/anzati Owned by: anotherguest
Priority: normal Component: Engine: SCUMM
Keywords: Cc:
Game: Sam and Max

Description

ScummVM version:

Symbian S60 Version 3 binary 0.9.1 (Oct 24 2006 23:54:31)

Bug details, including instructions on reproducing:

Sam and Max closes (resets back to my phone menu, ScummVM closes completly) after you have rode the cable car to the restaurant at the top of the ball of twine, during the animation where max points out that there is a loose thread.

Language of game:

English

Version of game:

Floppy

Platform and Compiler

DOS

Ticket imported from: #1600313. Ticket imported from: bugs/2921.

Attachments (1)

samnmax.s01 (31.5 KB ) - added by SF/anzati 14 years ago.
Sam & Max Save

Download all attachments as: .zip

Change History (15)

comment:1 by fingolfin, 14 years ago

Owner: set to anotherguest
Summary: SAMNMAX Closes at ball of twine on Symbian OS Nokia N73SYMBIAN/SAM: Closes at ball of twine on Symbian OS Nokia N73

comment:2 by fingolfin, 14 years ago

Please attach a save game with which one can reproduce the issue.

Also, can you reproduce the issue on your desktop computer (running Windows, I'd guess?) ? Using that same savegame, I mean...

by SF/anzati, 14 years ago

Attachment: samnmax.s01 added

Sam & Max Save

comment:3 by SF/anzati, 14 years ago

I have now attached the save game, if you just enter the cable car it should close ScummVM while on a shot of the loose thread.

I have tested this on my PC through Windows and the game doesn't crash. This has allowed me to create a new save, that should allow me to progress past the crash point once transferred to my phone.

comment:4 by fingolfin, 14 years ago

So the bug is Symbian specific.

Maybe it's also caused by OSystem::grabRawScreen() not being implemented? Just a wild guess, I haven't been able to test this savegame yet.

comment:5 by SF/anzati, 14 years ago

I have done some reading up on the OSystem::grabRawScreen()issue, and it does sond very similar to those reports. The work around of playing that section on PC, mentioned on one of the reports regarding DOTT, did also work for me. I haven't had the issue so far with DOTT, although I am yet to complete the game on my phone, so it is possible the issue will also crop up there. I have a save close to the cart washing sequence mentioned in another report as a crash point in DOTT, so I will try this later today.

comment:6 by SF/anzati, 14 years ago

I have tested DOTT and I go get the same crash, so I'm quite convinced this is the same OSystem::grabRawScreen()issue as the other bug reports, sorry to have wasted your time reporting an occourance of a known issue.

comment:7 by anotherguest, 14 years ago

I will use a crash tool on a S60v2 phone to try to reproduce the crash. Since the SDL backend is used grabrawscreen is implemented using that, and should n't be the main source of problems.

comment:8 by fingolfin, 14 years ago

Could it be a memory problem? I.e. grabRawScreen allocates yet another screen surface, maybe that malloc fails? As you can see, I have no idea how tight memory on these Symbian systems really is...

comment:9 by SF/paganguru, 14 years ago

I came here looking for help with the same problem, except that I am using a PSP with CD version of the game. Max says, "Hey, look." It shows the ball of twine, the music stops and the PSP turns itself off.

comment:10 by sev-, 13 years ago

What is the status of this item?

comment:11 by fingolfin, 13 years ago

What is the status of this item? Does it still occur in 0.10.0 ?

In addition, note that in SVN (i.e. post-0.10.0), we made changes to the code which *might* affect this. So if the problem still occurs in 0.10.0, it would be nice if somebody could test with an SVN build to see if the issue occurs there, too.

comment:12 by fingolfin, 13 years ago

Status: newpending

comment:13 by SF/sf-robot, 13 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:14 by SF/sf-robot, 13 years ago

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