"I'm running the very latest Retrospect, 6.0.212 (the Tiger version), with the latest drivers and clients. removed from /Library/Startup Items), the problem does not occur. By trying many different system configurations, I've narrowed down the root cause to Retrospect's RetroRun. The specific point of onset is variable, anywhere from 1 hour to 24 hours after reboot. "By leaving Activity Monitor open, I have repeatably captured the cause of the unresponsiveness: at some point, very suddenly, literally hundreds of cron processes spawn, all owned by root. This led to me look for a process usage overrun.
Attempting to launch an app results in an infinitely bouncing dock icon, plus a helpful 'proc: table is full' message in the system.log. No applications can be launched, quit, etc. Soon after, all other applications become unresponsive. Specifically, what happens is that the frontmost application suddenly stops responding, with the spinning beachball/busy cursor appearing. "When Retrospect's RetroRun is enabled as a startup item, my Mirrored Door Drive (aka Wind Tunnel) Dual 1 GHz G4 Powermac becomes unresponsive on a daily basis.
One such item identified as a potential cause of system slow-down, and eventually full blown unresponsiveness, is the RetroRun component of Dantz' Retrospect. Problems with Retrospect 'RetroRun' startup item - causes unresponsiveness Users experiencing sudden system unresponsiveness under Mac OS X 10.4.x should check for errant items located in the /Library/Startup Items folder.
0 kommentar(er)
