You can make a difference in the Apple Support Community!

When you sign up with your Apple Account, you can provide valuable feedback to other community members by upvoting helpful replies and User Tips.

Looks like no one’s replied in a while. To start the conversation again, simply ask a new question.

User profile for user: valevari
valevari Author
User level: Level 1
28 points

'ReportCrash' process in activity monitor popping out with high cpu usage

Hello,
I've upgraded my macbook white to Leopard and did all the usual mantainance routines.

However my fan noise has gone up considerably from Tiger infact fan is always spinning at around 6000 rpm. CPU temp is about 60 degree.

I've just Firefox open and looking at the activity monitor for possible CPU eaters the only abnormal thing I can find is this 'ReportCrash' process continuosly popping in and out and taking between 50 and 99% of CPU usage.

Any ideas why and if it's indeed a normal behaviour?

thanks in advance

val

macbook white 2Ghz Core 2 Duo, Mac OS X (10.5.8), Fireface 400

Posted on May 1, 2010 4:27 AM

Reply
Question marked as Top-ranking reply
User profile for user: Camelot
Camelot
User level: Level 9
55,305 points

Posted on May 1, 2010 10:20 AM

The CrashReporter kicks in any time an application crashes. It saves the application state to (hopefully) aid the developer in working out why the app crashed.

In your case it sounds like you have some process that's launching, crashing (and invoking CrashReporter) and then re-launching, repeating this cycle ad infinitum.

You need to identify which process is triggering this cycle and stop it.

Fortunately CrashReporter is pretty verbose in its logging and given the frequency it shouldn't be hard to find the culprit. Just look towards the end of your system.log, either via /Applications/Utilities/Console.app or via the terminal.
View in context
6 replies
Question marked as Top-ranking reply
User profile for user: Camelot
Camelot
User level: Level 9
55,305 points

May 1, 2010 10:20 AM in response to valevari

The CrashReporter kicks in any time an application crashes. It saves the application state to (hopefully) aid the developer in working out why the app crashed.

In your case it sounds like you have some process that's launching, crashing (and invoking CrashReporter) and then re-launching, repeating this cycle ad infinitum.

You need to identify which process is triggering this cycle and stop it.

Fortunately CrashReporter is pretty verbose in its logging and given the frequency it shouldn't be hard to find the culprit. Just look towards the end of your system.log, either via /Applications/Utilities/Console.app or via the terminal.
Reply
User profile for user: valevari
valevari Author
User level: Level 1
28 points

May 1, 2010 12:55 PM in response to valevari

ok i've looked into the logs and what seems to trigger the cicle is 'qmasterd'.. I must admit I had never heard of it before.

It's not in the login items list and i just have Firefox running.
I'm running no mac clusters and as far as I know the only software that I have that could use Qmaster is Logic Pro.

So i'm wondering: how to kill this cicle? trashing Qmaster app perhaps?

thanks again
Reply
User profile for user: Camelot
Camelot
User level: Level 9
55,305 points

May 2, 2010 9:40 AM in response to valevari

QMaster is the distributed processing engine of Final Cut Studio - it allows Final Cut Pro/Shake and similar projects to be rendered/processed across a range of computers to improve processing time.

If this machine is part of a cluster of machines running Final Cut Studio then removing this might impact your workflow (although it sounds like it wasn't running correctly in the first place anyway). You'll need to decide whether or not to try and re-instate this process.
Reply

'ReportCrash' process in activity monitor popping out with high cpu usage

Welcome to Apple Support Community
A forum where Apple customers help each other with their products. Get started with your Apple Account.
Learn more Sign up