This discussion is archived
23294 Views 98 Replies Latest reply: Dec 27, 2008 5:57 AM by CT
Currently Being ModeratedSep 18, 2008 8:44 AM (in response to bookmac)Excellent! That was my problem exactly. My powerpc process was "privoxy", and for some reason it was causing launchd to consume 1.5 GB of RAM, bringing my system to a crawl. Killing privoxy (the only powerpc program) fixed it.Mac OS X (10.5.4)
Currently Being ModeratedOct 4, 2008 6:59 AM (in response to bookmac)So I am the latest victim to syslogd terror
Here is my repeating log
Oct 4 16:55:00 Macintosh ScreenSaverEngine: * <QCView: 0x13bbd0>: Render failed at time 5.133353s
Oct 4 16:55:00 Macintosh ScreenSaverEngine: * Message from <QCPatch = 0x04D8DE20 "Patch_8">:\nExecution failed at time 5.167
Oct 4 16:55:00 Macintosh ScreenSaverEngine: * Message from <QCPatch = 0x044D6AC0 "(null)">:\nExecution failed at time 5.167
And this happens when i try to change a screen saver in system preferences or when stopping the screen saver after it came into effect. And it all used to work fine upto two days ago when i got my disk full and had to hard-shutdown. May be the latest java update ? whatever.
Here is the crashreporter log for the screensaver :
Thread 0 Crashed:
2 ...QuartzComposer.ExtraPatches 0x04380a2c 0x4375000 + 47660
3 com.apple.QuartzComposer 0x92664254 -[QCPatch(Private) _cleanup] + 264
4 com.apple.QuartzComposer 0x9265958c -[GFList makeObjectsPerformSelector:] + 96
5 com.apple.QuartzComposer 0x926641a8 -[QCPatch(Private) _cleanup] + 92
6 com.apple.QuartzComposer 0x9265958c -[GFList makeObjectsPerformSelector:] + 96
7 com.apple.QuartzComposer 0x926641a8 -[QCPatch(Private) _cleanup] + 92
8 com.apple.QuartzComposer 0x9265958c -[GFList makeObjectsPerformSelector:] + 96
9 com.apple.QuartzComposer 0x926641a8 -[QCPatch(Private) _cleanup] + 92
10 com.apple.QuartzComposer 0x92664070 -[QCContext stopRenderingPatch:] + 132
11 com.apple.QuartzComposer 0x92663fd4 -[QCGraphicsContext stopRenderingPatch:] + 80
Here is my suggestion (not a fix) :
1. use terminal to stop the syslogd and remove the log files asl.log and system.log and restart syslogd - it helps mostly except sometimes it resumes cpu usage (simply changing the error-reporting-level from 5 to 4 doesn't help)
2. repair disk permissions and clean up system caches - this has helped me so far : no cpu eating by syslogd
3. update the app in question or avoid using it : i have still to do it
4. archive and install - this should be the last resort.PowerBook G4 15", Mac OS X (10.5.5), 1.5GHz/512MB/80GB
Currently Being ModeratedOct 4, 2008 2:34 PM (in response to kanny)It turned out that the real culprit was a specific Screen Saver and not the ScreenSaverEngine.app
But the problem was i couldn't even change the screensaver as it crashed and syslogged enormously. Finally i had to pull out the com.apple.screensaver.12345678abcd.plist from my backup and replaced the corrupted one. And huh, the problem is gone.
So syslogd is not the root cause of high cpu usage but a corrupt app and its pref file are. Despite of this finding, i would have wished a more decent behaviour from syslogd in terms of not logging the same message repeatedly more than a certain no of times.PowerBook G4 15", Mac OS X (10.5.5), 1.5GHz/512MB/80GB
Currently Being ModeratedOct 12, 2008 2:58 AM (in response to bookmac)I've had this problem ever since installing Leopard. My issue seems to be related to using a Huawei Mobile Broadband dongle. It sends the system crazy. I used every fix I could find and had everything working fine until the latest security update from Apple (2008-007). Now, having a nightmare. Had to kill spotlight as mds is going nuts and syslog too. APPLE, WHAT THE F*!!!!!!! Clearly not enough of us are having these problems to warrant a proper fix. Jeesh12" Powerbook G4, Mac OS X (10.5.5)
Currently Being ModeratedNov 14, 2008 4:22 AM (in response to Alexander Grove)I see that same problem - upgraded from Tiger to Leopard 10.5.5 and whenever the HUAWEI Mobile appliation is open the mds process takes huge amounts of CPU. Note I don't even have to be connected to the mobile network, just having the app open causes it.
Is it because the app is quite verbose in logging to system.log? If so, how can I stop it causing mds going crazy.Macbook 2GHZ, Mac OS X (10.5.5)
Currently Being ModeratedNov 14, 2008 7:17 AM (in response to dohrayme72)Have begun having the same syslogd hogging resources problem. One recommendation was to check for runaway apps or apps writing excessively. Another had to do with memory hogs. Don't see any of the above. However, I have the following from the system crash reporter ---
Since it sounds like most of us have never run into this before, it sure seems as though its got to be an OS-X bug. Has Apple weighed in at all on this (no, i didn't read through all 7 pages of messages.)
teMini Mac e/w 1.25 GB, Mac OS X (10.5)
Currently Being ModeratedNov 25, 2008 10:35 PM (in response to bookmac)Got the same problem on my Macbook.... (Leopard 10.5.5).
Apple! Wake up and at least comment on this??MacBook, Powerbook G4 & iMac, Mac OS X (10.4.7)
Currently Being ModeratedDec 26, 2008 7:45 PM (in response to bookmac)I downloaded Maintidgit, (http://mac.softpedia.com/get/Dashboard-Widgets/Status-Info/Maintidget.shtml) ran the scripts and seem to have solved the problem. My problem appears to have started on the same day as I downloaded the 10.5.6 updateMacBook 1,1, Mac OS X (10.5.6)
Currently Being ModeratedDec 27, 2008 5:57 AM (in response to DDdaviking)
Got the same problem on my Macbook.... (Leopard 10.5.5).
Apple! Wake up and at least comment on this??
No comment.MacBookPro5,1, Titanium Powerbook,, Mac OS X (10.5.6)