Opened 17 years ago
Closed 16 years ago
#2722 closed defect (fixed)
WINCE: BS1 Crash while starting game
|Reported by:||SF/bigbadbruce||Owned by:||SF/knakos|
|Cc:||Game:||Broken Sword 1|
WCE: V9 Official and 2nd of July release. Broken Sword 1, English with compressed files
In the Official Release the error occured just after the video finished (for some reason for me the video doesn't play smooth) In the 2nd of July release, the problem occures at the very start, almost as if it cannot load the files.
This has occured on both a HX4700 and a Compaq iPaq H3900
See the attached file for the error logs
Ticket imported from: #1518139. Ticket imported from: bugs/2722.
Change History (10)
by , 17 years ago
comment:1 by , 17 years ago
|Summary:||Crash while starting game → WINCE/BS1: Crash while starting game|
comment:2 by , 17 years ago
This happens also on a WinCE 5.0 machine (Dell AXIM X51v). The condition for this to happen is when a game has MP3 or OGG sound. Deleting the MP3 or OGG files allows the game to run fine (albeit without music / soundtrack, which kind of defeats the purpose).
I suspect this is a bug where the VM calls the MP3 or OGG library which isn't present on the machine, and thus crashes.
comment:3 by , 17 years ago
EDIT - With version 9a I get the error, but the mp3 audio still plays while the error is displayd but no video is shown.
comment:4 by , 17 years ago
lowering the priority and heading for closing this one. the game does not crash given enough memory it seems. also video playback is very hard on the cpu (mpeg decode 640x480, yuv convert 640x480, resample and blit to 320x240). will check up on it once more, before giving up.
comment:5 by , 17 years ago
|Priority:||normal → low|
|Summary:||WINCE/BS1: Crash while starting game → WINCE: BS1 Crash while starting game|
comment:6 by , 16 years ago
Would it be possible to modify the port such that it displays a nice error message ("Out of memory") before quitting, as opposed to just silently crashing?
Maybe by overriding the malloc/new functions, inserting a check for allocation failure? If that is not possible, we could try to modify memory intensive spots (like the video decoders) to put additional checks around their memory allocation routines (displaying an error dialog if a malloc failed) ?
comment:7 by , 16 years ago
Good ideas Fingolfin. Will probably implement some/all of these. BTW, I still haven't found the time to re-verify this bug. Will get around to doing it soon.
comment:8 by , 16 years ago
|Status:||new → closed|
comment:9 by , 16 years ago
Working OK over here. wait for 0.9.1 and reopen if necessary.