Mikuro
Crotchety UI Nitpicker
Ever since I upgraded to Leopard, I've noticed something strange every time an application crashes. Whereas in Tiger the application would simply disappear, in Leopard I get a spinning beachball, my CPU usage soars, and my disk thrashes. This goes on for about 30 seconds, and THEN the application disappears.
When I take a look in Activity Monitor to see what's going on, I see two processes using large amounts of CPU time: CrashReporter and spindump. I believe CrashReporter existed in Tiger, but I don't recall seeing spindump before.
I went into Console to check the logs, and nothing seems out of place. There were some crash reports there, same as in Tiger. Spindump left a message saying "/usr/sbin/spindump[22285] process 18699 is being monitored" in the system log (18699 being the ID of the crashing program).
This delay and resource hogging is much more annoying than the crash itself. Is there any way to disable these processes?
I have already set OS X not to alert me when application crash (using TinkerTool). This did not affect CrashReporter's or spindump's performance, though.
And has anyone else noticed this problem?
When I take a look in Activity Monitor to see what's going on, I see two processes using large amounts of CPU time: CrashReporter and spindump. I believe CrashReporter existed in Tiger, but I don't recall seeing spindump before.
I went into Console to check the logs, and nothing seems out of place. There were some crash reports there, same as in Tiger. Spindump left a message saying "/usr/sbin/spindump[22285] process 18699 is being monitored" in the system log (18699 being the ID of the crashing program).
This delay and resource hogging is much more annoying than the crash itself. Is there any way to disable these processes?
I have already set OS X not to alert me when application crash (using TinkerTool). This did not affect CrashReporter's or spindump's performance, though.
And has anyone else noticed this problem?