Keeps on crashing on Mac (Snow Leopard 10.6.1)

[pmat]

As said in the title, my WZ 2100 v 2.2.2 doesn't stop crashing when I'm playing the solo campaign. I can't figure out how to reproduce the crash.

It occurs some times while playing skirmish as well.

I'm the only one with such problems ?

System :
Mac OS X 10.6.1 on iMac
Intel Core 2 Duo 2,4 GHz
2 Go RAM
ATI Radeon HD 2600 (256Mo VRAM)

[Zarel]

Can you copy/paste the crash details here?

[pmat]

The crash report comes from Mac OS X, next time I'll copy the text here.

[Zarel]

The crash report comes from Mac OS X, next time I'll copy the text here.

Yes, do that.

[pmat]

Here's the crash details (mission 17 I guess) on wz 2.2.2.

Hope this helps.

[pmat]

Another crash report

[Zarel]

It looks possible to fix. I'll try it.

[pmat]

Another crash report

[pmat]

Same mission...

[pmat]

During Skirmish game.

I hope all these files will help...

[-Kosh-]

Here's the crash details (mission 17 I guess) on wz 2.2.2.

Hope this helps.

Most all your issues are because someone compiled the mac builds incorrectly. I assume they did not want the game to puke on asserts?

Whatever the intent of the builder, the problem in many of your crash reports has to do with the game that can not figure out what you clicked on.

dealWithRMB + 1385 , dealWithLMBObject + 2761, dealWithRMB + 1385 all deal with what you clicked on.
droidOnMap + 6 some kind of check to see if the droid is on the map
and the other one looks to be fixed but your not using the latest version of warzone, which is 2.2.3.

How are you running warzone? Looks to me like half the information needed to fix the 'what you clicked on' is not in those crash dumps so it must be trying to dump it to stderr? If that is indeed the case, then you must run warzone from the terminal so it prints the information the developers can use to fix this issue.

It would print out one of these things

Code: Select all

ASSERT(false, "Weird selection from LMB - type of clicked object is %d", (int)psClickedOn->type);
ASSERT(!"unknown object position type", "Unknown type from checkMouseLoc");
or 
ASSERT(psClickedOn->type == OBJ_FEATURE, "Weird selection from RMB - type of clicked object is %d", (int)psClickedOn->type);

Devs, why is the mac crash dump different than that of windows & linux, which look to be the exact same?

Hope that helps.

[heatwave]

It looks possible to fix. I'll try it.

It astounds me that anyone can decipher that stuff. Bravo.

[Zarel]

It astounds me that anyone can decipher that stuff. Bravo.

The important part is that you don't need to understand all of it, you just to understand enough to know what's wrong. Usually, all that takes is the stack trace.

[pmat]

Unfortunately I installed Warzone using the DMG file provided in the download section.
The only crash report I get is the one displayed by Mac OS X after the application quit.

I may try to run the game via the Terminal, hoping it will be more "verbose"...

Looks like the game crashes more often when playing on map containing civilian buildings (intact or destroyed).

I often destroy all of them on my way because tanks get blocked on them. I noticed that the scare located at the center of the building can't be built on. Did I click on on of thoses scares ?

(Sorry english is not my primary language, hope you'll understand )

[pmat]

I launched WZ into the Terminal, here's the crash report.

I don't know who is this user "freddie"

XXXX@Mac:~$ /Applications/Warzone.app/Contents/MacOS/Warzone
info |07:56:53: [rebuildSearchPath] * Failed to remove path /data/ again
info |07:56:53: [rebuildSearchPath] * Failed to remove path /share/warzone2100/ again
error |07:56:58: [scrValDefLoad] Sound ID not available not found
last message repeated 2 times
error |08:03:03: [dealWithLMBObject] Weird selection from LMB - type of clicked object is -1775080237
error |08:03:03: [dealWithLMBObject] Assert in Warzone: /Users/freddie/Documents/Programming/2.2.2/macosx/../src/display.c:2180 (0), last script event: 'N/A'
/Users/freddie/Documents/Programming/2.2.2/macosx/../src/display.c:2180: failed assertion `0'
Abort trap

The Apple crash report from Mac Os X is included aswell.