Mac Crashes
Process: cider_noui [993]
Path: /Applications/City of Heroes.app/Contents/MacOS/cider_noui
Identifier: com.transgaming.cityofheroes
Version: City of Heroes (1)
Build Info: City of Heroes-4462~4462
Code Type: X86 (Native)
Parent Process: ??? [1]
Date/Time: 2010-09-25 23:31:02.969 -0400
OS Version: Mac OS X 10.6.4 (10F2056)
Report Version: 6
Interval Since Last Report: 252787 sec
Crashes Since Last Report: 4
Per-App Interval Since Last Report: 139907 sec
Per-App Crashes Since Last Report: 4
Anonymous UUID: F2846B40-9FFD-46FC-8232-46AD62D2857E
That is what keeps crashing me I noticed.
1. Why Soft Cap is Important : http://dechskaison.blogspot.com/2011...important.html
2. Limits: http://paragonwiki.com/wiki/Limits
3. Attack Mechanics: http://wiki.cohtitan.com/wiki/Attack_Mechanics
4. Rule of Five: http://wiki.cohtitan.com/wiki/Rule_o...e_Law_of_Fives
You have a different (older) OS X build than I do - did you install all the latest software updates?
Manga @ Triumph
"Meanwhile In The Halls Of Titan"...Titan Network Working To Save City Of Heroes
Save Paragon City! Efforts Coordination
{unrelated to any of the above}
Due to the information in this thread, I went and checked which version of the Mac Client I'm (still) using.
City of Heroes v1.0.3068
Created: Monday, January 5, 2009 1:37 PM
Modified: Tuesday, November 10, 2009 6:04 PM
I'm spending about 7 hours today, downloading the 3.6 gig Mac Client accessible from my NCSoft Account Login page (where you see your subscription and cards/perks/boosters applied to your account) ... since it sounds like I *REALLY* need to update to 4462 (as specified in OP).
I have the lastest OS X updates and the most recent client software. Still crashes at least one time every session.
Why is there no official word from the devs about this? Why is there no plan to get this fixed?
Ideally, the tank will die precisely as everyone else starts fighting, allowing aggro to be spread evenly among the blaster. -seebs, "How to Suck at CoH/CoV" Guide
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.
Manga @ Triumph
"Meanwhile In The Halls Of Titan"...Titan Network Working To Save City Of Heroes
Save Paragon City! Efforts Coordination
Cider is a kluge. It's a crappy way to avoid making what we really need/want: a Mac native client. The biggest MMO in the world, The One That Shall Not Be Named, has one, and they maintain the same code for all platforms.
We should expect no less.
Ideally, the tank will die precisely as everyone else starts fighting, allowing aggro to be spread evenly among the blaster. -seebs, "How to Suck at CoH/CoV" Guide
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.
Manga @ Triumph
"Meanwhile In The Halls Of Titan"...Titan Network Working To Save City Of Heroes
Save Paragon City! Efforts Coordination
City of Heroes v1.0.3068
Created: Monday, January 5, 2009 1:37 PM Modified: Tuesday, November 10, 2009 6:04 PM |
Created: Monday, January 5, 2009 1:37 PM
Modified: Tuesday, November 10, 2009 6:04 PM
Interesting that the Created/Modified dates and times don't change when updating the base client to a higher version. Reinstalling/toploading the client worked like a charm. I have to agree that the 4462 version fixed a LOT of crud. I now get a proper game mouse cursor without needing to Alt-Tab to enforce *some* kind of non-typical (and practically invisible BLACK) cursor icon in the game along with hand icons (orange instead of blue). I've got enough frame rate now to kick my graphics settings up ever so slightly into *some* of the ultra mode goodies (like shadows) without dropping down below 15 FPS routinely (which is a PAIN when navigating while ninja jumping).
One peculiar habit which the client has picked up though is pausing for more than a second while loading the character screen after selecting server. No idea why it does that, or what could cause such a condition. It is however somewhat similar to the way the client just ... hangs ... any time I approach WW in Talos, close enough to cause a network panic lag as the server tries to transmit data on all those characters standing around in WW messing with the Auction House. Really wish there was some way Paragon Studios could code those "Load Dozens of Characters NAO!" moments so they involved a more graceful impact on client performance.
1. Why Soft Cap is Important : http://dechskaison.blogspot.com/2011...important.html
2. Limits: http://paragonwiki.com/wiki/Limits
3. Attack Mechanics: http://wiki.cohtitan.com/wiki/Attack_Mechanics
4. Rule of Five: http://wiki.cohtitan.com/wiki/Rule_o...e_Law_of_Fives
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.
Edited to add: I trashed my game prefs recently and did everything your troubleshooting guide recommended. Should be all the same save for what startup items we have, I suppose.
My guides:Dark Melee/Dark Armor/Soul Mastery, Illusion Control/Kinetics/Primal Forces Mastery, Electric Armor
"Dark Armor is a complete waste as a tanking set."