Extremely crashy on newer Mac?

I've noticed that CoH seems to be awfully crashy on my Mac -- it crashes several times a night. I've got one of this year's newer MBPs, with the nVidia 330M. My spouse plays on an older Mac with a GeForce 8600M, and has had no crashing problems at all. Crashing is especially bad when in crowded areas or loading a lot of textures.

The only obvious difference, apart from the newer video card, is that my machine has 8GB of RAM, which could be causing WINE to pick up enough memory to trigger some bugs that would otherwise be hidden. Anyone seen this? It's obvious that the game isn't generically this crashy, but at the same time, this machine can run programs other than CoH without any problems...

Try turning setting Geometry Buffers to Disabled and see if that improves things for you. I've been testing that setting for a while now after it was recommended by another poster.

Thanks, I'll try that! It doesn't immediately suggest why I would have this problem on this mac, but my spouse wouldn't on an older mac, but it's a thing to try nonetheless.

I have the same super-crashiness on my 08 24" iMac. Turning off Geometry Buffers helped, as does /unloadgfx every 20-30 minutes (or more, if there's a lot of zone changes). It's fairly stable, but this feels like a hacky, beta-way to get it to a playable state. If I don't do those things, it crashes every 10-15 minutes or less.

The general shoddiness of the OSX port is probably why I won't keep my subscription (I resubbed for a month). It has been crashy every time I've tried it since it was released. The issues are persistant, and the only fixes are from other players on the message board. Don't get me wrong, those users are great! But that is a pisspoor way to support a game.

I realise that Transgaming may be in charge of the OSX client code (wrapper/cider et cetera) but it's NCSoft's responsibility to kick 'em in the *** and make sure the damn thing works.

Well, given that it seems to be stable enough for my spouse (who is playing 3-4 hour sessions without a crash), it's hard for me to blame Transgaming alone; clearly, there's something special. Either it's a bug triggered by having too much RAM available (WINE is known to act weird if you give it a machine with >4GB sometimes), or it's a driver problem, probably.

Wow. You got it -- turning off Geometry Buffers, at a slight cost in pretty (there's some occasional stray pixels between polygons now), seems to have removed the crashing. Went through a costume contest and a longish mission arc, no problems.

Actually those stray pixels are caused by Vertical Sync not working. That should be repaired soon(tm).

Huh! Weird, because I was pretty sure I hadn't seen them before.

Anyway, went back to full resolution, turned on a couple of other features, all is well, everything stays stable. Yayyyyyy!