CuppaManga

I agree, that would be ideal. However, at the time CoH for Mac went into beta, Paragon Studios was nearly all Windows, and lacked the resources to expand into Mac development without delaying other things like timely release of new issues. So a partnership with Transgaming was born.

Blizzard made the decision to develop both for Mac and Windows long before their current games existed. They already had a solid base of both Windows and Mac developers.

P.S. Actually Blizzard's code isn't identical on both platforms. They have two code bases, one for Mac and one for Windows, that share game assets and scripts. Maintaining a game that way is very expensive and resource intensive.

One crash per session is about average. I'm troubleshooting crashes that are more frequent than that by trying to figure out a pattern.

The once-per-session crashes are an inevitability until something fundamental in Cider is fixed so it allocates and releases memory correctly. Since Cider is made up of so many component parts (some of which are owned by Transgaming, some by Paragon Studios, and some by the opensource WINE project) it's hard to predict when that will be fixed.

Good news is I suspect someone may be working on it, because the Assertion Failure many of you have been seeing is likely caused by the crashes going into debugging without a debugger present.

You have a different (older) OS X build than I do - did you install all the latest software updates?

Fixed above.

You're using an old Mac client build. Read my Troubleshooting guide (in the signature) for more info.

I'm currently trying to find a pattern with these Assertion Failure issues - it seems it's not just on nVidia systems anymore. Which Mac game build are you using? (check the original post to see how to figure that out).

You listed your Macbook Pro as a Core i7 with nVidia 300M and 256 mb of VRAM - is that correct? The Core i7 model has 512 mb of VRAM according to the Apple Store (that's what I have). I'm checking to see of maybe the amount of VRAM has to do with the crashes.

I see two errors in the log.

The first I'm familiar with - Error 12 means not enough memory handles available, pretty much the cause of every CoH Mac crash. For some reason Cider (since forever) hasn't been releasing video memory properly, which is why /reloadgfx works (it forces a release of all of it) and why it causes a crash eventually. The increased frequency of the crashes is a mystery so far.

And the 2nd error seems to be because Transgaming left some debugging code in there and it's broken, which explains the Assertion Failure.

Even so, if we're using the same Mac and the same OS version (you did run Software Update didn't you?) and the same client build (4462?) it should behave the same unless you have something drastically different from me, or our game Preferences are different somehow.

Do you have Geometry Buffers disabled? And do you have World Detail set to 100% or less? And is FSAA off (it causes more RAM allocations)?

Hmm...you have TimeMachine turned on. You're the second person to have a possible correlation between that and CoH. The plot thickens...

Just out of curiosity Nalrok - are you booted in 32-bit or 64-bit mode?

If you don't know it's probably 32-bit. I have mine booted in 64-bit mode. Maybe that's the difference, since our hardware should be identical otherwise.

Which Macbook model are you using? Does it have Intel or nVidia graphics?

Yes, you can pan around by holding down the scroll wheel (if your mouse has it). The PgUp/PgDn/Home/End keys on a Macbook exist but they're unlabeled for some reason - hold down the Fn key just left of the Control, and then use the arrow keys.

My signature has a link to my Mac guide, read it for lots more info.

For some reason Cider (the translation engine that makes CoH work on a Mac) uses its own fixed gamma setting. It can't really be changed at the moment.

That should not be happening, it's not because you bought a Mac. Contact Support via help.ncsoft.com, they should be able to fix the problem.

The next step has two methods.

If you know pretty well how to check if you have anything loading at Mac startup, or if you have any 3rd-party extensions installed, list them here. It'll save me some time that way.

Or if you don't know how to do that, open System Profiler (Applications > Utilities) and use the Save As option to save a file as RTF. Open the document in Textedit and remove the Serial Number and UUID - I don't need them and they shouldn't be public. Then share the document somewhere (sorry, I don't actually know where a text document can be shared) and send me a PM with its location - don't post the location here.

As a bonus, if I find there's an Apple related bug I can use the same file to submit to their bug tracker as well.

Have either of you run a Verify Disk in Disk Utility recently? Do you have any 3rd party RAM installed or just Apple branded? Did you check Software Update to make sure you're all up to date?

And so I can see if there's a pattern, both of you please post your Mac model and year, RAM, and video processor type (ATI, Intel, or nVidia and model).

Also send Support requests via help.ncsoft.com. Their reply might not be very helpful right away, but it starts a tracking process that will get the devs' attention.

Post the last few lines of your console log (Applications > Utilities > Console) after a crash, it might provide a useful clue. Also post your Mac model, RAM, video along with it.

If it does that again:

1. Open Console (Applications > Utilities) and click the Show Log List icon at the top. Look in the Files > /Library/Logs > PanicReporter section. If there's a .panic log there with a recent date as its name, post it here.

2. If there's no .panic log, select system.log at the top of the Files list and post the last few lines here.

Read this:

http://boards.cityofheroes.com/showthread.php?t=238194

and also the troubleshooting thread in my signature.

Is the whole computer freezing or just the game?

Yes, you definitely need to update if you're using 3068.

Let's see your CoH build, Mac model, RAM, video type, etc...