Re: crash reporter slowing down relaunches
Re: crash reporter slowing down relaunches
- Subject: Re: crash reporter slowing down relaunches
- From: Chris Espinosa <email@hidden>
- Date: Wed, 6 Feb 2008 10:33:39 -0800
On Feb 6, 2008, at 10:13 AM, Stuart Smith wrote: I have a crashy application, which I am debugging on 10.5.1 using Xcode 2.5.
If I quit the application normally, or click the Terminate button in the Xcode debugger window, all is well – the application quits, or is terminated, quickly.
However, if the application causes e.g. an access exception and lands in the debugger, I usually poke around to find the cause, then terminate the application using the big red Terminate button in the Xcode debugger window. It then takes about 30s on a Mac Pro quad core before the application is no longer active according to the Dock. During that time, an application called Report Crash (or Crash Reporter, I forget) is using significant amounts of CPU. I can quit that application from Activity Monitor and get back to work sooner, but I’d rather not have to.
Does anyone else experience this behavior, and does anyone know how to prevent it? I don’t want Crash Reporter to write me a crash log under these circumstances, but that seems to be what it is doing. As I said, this doesn’t normally happen if I simply force-quit the application from the debugger – it happens if the application crashes, then lands in the debugger, and then I force-quit it.
Chris |
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden