Adium keeps spamming to system.log - syslogd at 20% CPU !!

[jan.eisklar]

As I said, Adium keeps spamming the system.log which is causing the syslogd to take up 20% of the CPU. I did deactivate syslogd for now, but this definitely should be fixed as soon as possible.

It logs about 4kb of data every second regardless of whether I'm connected or not.

This is what Adium's spam log entries look like:

Jul 28 10:42:35 A319 Adium[319]: Error Domain=org.brautaset.JSON.ErrorDomain Code=3 UserInfo=0x14164730 "Unrecognised leading character"
Jul 28 10:42:35 A319 Adium[319]: Error Domain=org.brautaset.JSON.ErrorDomain Code=3 UserInfo=0x12423d90 "Unrecognised leading character"
Jul 28 10:42:35 A319 Adium[319]: Error Domain=org.brautaset.JSON.ErrorDomain Code=3 UserInfo=0x13f32fa0 "Unrecognised leading character"
Jul 28 10:42:35 A319 Adium[319]: Error Domain=org.brautaset.JSON.ErrorDomain Code=3 UserInfo=0x124ee740 "Unrecognised leading character"
Jul 28 10:42:35 A319 Adium[319]: Error Domain=org.brautaset.JSON.ErrorDomain Code=3 UserInfo=0x1245dc00 "Unrecognised leading character"
Jul 28 10:42:35 A319 Adium[319]: Error Domain=org.brautaset.JSON.ErrorDomain Code=3 UserInfo=0x1242a700 "Unrecognised leading character"
Jul 28 10:42:35 A319 Adium[319]: Error Domain=org.brautaset.JSON.ErrorDomain Code=3 UserInfo=0x11c3dba0 "Unrecognised leading character"
Jul 28 10:42:35 A319 Adium[319]: Error Domain=org.brautaset.JSON.ErrorDomain Code=3 UserInfo=0x13f88ab0 "Unrecognised leading character"
Jul 28 10:42:35 A319 Adium[319]: Error Domain=org.brautaset.JSON.ErrorDomain Code=3 UserInfo=0x1246af30 "Unrecognised leading character"
Jul 28 10:42:35 A319 Adium[319]: Error Domain=org.brautaset.JSON.ErrorDomain Code=3 UserInfo=0x11c3b5a0 "Unrecognised leading character"
Jul 28 10:42:35 A319 Adium[319]: Error Domain=org.brautaset.JSON.ErrorDomain Code=3 UserInfo=0x1242cab0 "Unrecognised leading character"
Jul 28 10:42:35 A319 Adium[319]: Error Domain=org.brautaset.JSON.ErrorDomain Code=3 UserInfo=0xde12f70 "Unrecognised leading character"
Jul 28 10:42:35 A319 Adium[319]: Error Domain=org.brautaset.JSON.ErrorDomain Code=3 UserInfo=0x11c58ad0 "Unrecognised leading character"
Jul 28 10:42:35 A319 Adium[319]: Error Domain=org.brautaset.JSON.ErrorDomain Code=3 UserInfo=0x13f88ab0 "Unrecognised leading character"
Jul 28 10:42:35 A319 Adium[319]: Error Domain=org.brautaset.JSON.ErrorDomain Code=3 UserInfo=0x1246af30 "Unrecognised leading character"
Jul 28 10:42:35 A319 Adium[319]: Error Domain=org.brautaset.JSON.ErrorDomain Code=3 UserInfo=0x14170d20 "Unrecognised leading character"

System: Macbook Pro Mac OS X 10.5.4 Adium 1.3b9

[evands]

What's the Adium Debug Window output at the same time?

[d-b]

I also have this problem with the current beta of Adium, Believe it has to do with Facebook, the debug window is full with lines like:

13:42:56: -[AIFacebookIncomingMessageManager connectionDidFinishLoading:]: Received (null)

[d-b]

What is weird is that my FB account is disconnected now and the logging still occurs. However, when I try to disable the account (either when it is disconnected or connected), the disable account menu option is not there (only Disconnect, Set to current Adium status and Custom). Finally after disabling the FB account from within the preferences window, I can verify that these entries in system.log and in the debug window still are printed. The FB account does not seem to be disabled fully even though it is set to disabled.

However, after a restart of Adium I got rid of this excessive logging.

[jan.eisklar]

If you restart Adium you get rid of it for a while, but it will start again. I tried several restarts, after ~1 minute it always restarted spamming the system.log.

The only way out is disabling syslogd.

[d-b]

How do you (temporarily) disable syslogd?

[jan.eisklar]

disable: sudo launchctl unload /System/Library/LaunchDaemons/com.apple.syslogd.plist

enable: sudo launchctl load /System/Library/LaunchDaemons/com.apple.syslogd.plist

[dankicksass]

From system.log

Aug 19 01:37:49 MacBook-Pro-2 Adium[419]: *** NSTimer ignoring exception 'Can't cache image' that raised during firing of timer with target 0x587430 and selector 'animateIcon:'
Aug 19 01:37:50: --- last message repeated 1757 times ---
Aug 19 01:37:50 MacBook-Pro-2 Adium[419]: *** NSTimer ignoring exception 'Can't cache image' that raised during firing of timer with target 0x54acb0 and selector 'flashTimer:'
Aug 19 01:37:50 MacBook-Pro-2 Adium[419]: *** NSTimer ignoring exception 'Can't cache image' that raised during firing of timer with target 0x587430 and selector 'animateIcon:'
Aug 19 01:47:23 MacBook-Pro-2 com.apple.launchd[1] (com.apple.syslogd[293]): Exited abnormally: Interrupt
Aug 19 01:37:50 MacBook-Pro-2 Adium[419]: *** NSTimer ignoring exception 'Can't cache image' that raised during firing of timer with target 0x587430 and selector 'animateIcon:'
Aug 19 01:48:08: --- last message repeated 127 times ---

High CPU usage, syslogd. I disabled. I use a message style with high transparency (etherial) and this all started when i was invited to a MSN group chat.

[dankicksass]

Adium itself is using high CPU too... 45%

[d-b]

Was 1.3 released without this bug being fixed? I think this bug should have very high priority, when this happens my computer (a fairly recent Macbook Pro) becomes more or less irresponsive and, I reckon, after a while Adium crashes due to the high load. Disabling the syslog is not something you can suggest to inexperienced users as a workaround.

[Robby]

dankicksass, please file a separate ticket for your issue (ReportingBugs). I've been told yours is a different one than jan.eisklar's.
So, jan.eisklar, is still problem still there for you in 1.3?
d-b, the developer I asked about this ticket said he isn't sure whether yours is the same problem.

[frett]

I'm still experiencing this bug with the final version of 1.3, if I get a chance I'll compile the latest version from svn with debugging enabled and try to get a debugging log for this bug.

[Centurion]

I have added some proxy log information to Ticket #10872 which appears to be a duplicate of this issue.

[owlgorithm]

I am having a similar problem. It appears when I use the Akkasone icon (from Xtras), but not when I use iAdiumBubble 2.1. It's logging like crazy -- syslogd is using about 65% of my available processing right now. Here's a snippet:

9/3/08 3:26:30 PM Adium[357] *** NSTimer ignoring exception 'Can't cache image' that raised during firing of timer with target 0x483220 and selector 'animateIcon:' 
9/3/08 3:26:30 PM Adium[357] *** NSTimer ignoring exception 'Can't cache image' that raised during firing of timer with target 0x483220 and selector 'animateIcon:' 
9/3/08 3:26:30 PM Adium[357] *** NSTimer ignoring exception 'Can't cache image' that raised during firing of timer with target 0x483220 and selector 'animateIcon:' 
9/3/08 3:26:30 PM Adium[357] *** NSTimer ignoring exception 'Can't cache image' that raised during firing of timer with target 0x483220 and selector 'animateIcon:' 
9/3/08 3:26:30 PM Adium[357] *** NSTimer ignoring exception 'Can't cache image' that raised during firing of timer with target 0x483220 and selector 'animateIcon:' 

I am using Adium 1.3 (final) on OS X 10.5.4.

[owlgorithm]

My mistake -- my message needs to go to the icon's author. My apologies!

[evands]

(In [25094]) Stop requesting incoming Facebook messages when Facebook disconnects. Fixes #10872. Fixes #10588. Both were symptoms of debug logging which would run amok when repeatedly faced with the invalid requests and invalid responses of requesting incoming messages for a disconnected Facebook account.

[evands]

(In [25095]) merged [25094]: Stop requesting incoming Facebook messages when Facebook disconnects. Fixes #10872. Fixes #10588. Both were symptoms of debug logging which would run amok when repeatedly faced with the invalid requests and invalid responses of requesting incoming messages for a disconnected Facebook account.

[d-b]

Is this really fixed? I still have this problem (Adium using 80-90% CPU, syslog is spammed) in 1.3.2

[Robby]

Hi d-b, I don't whether it is the same problem but look it's looks similar: #11257.

[d-b]

Actually, after looking closer at this, Adium no longer spams the logs. However, after networks problems, it still frequently uses 60-70% CPU and does something that forces DirectoryService to use around 20% CPU. Manually selecting Offline remedies the CPU usage.

[Robby]

Please check the (next beta) release of 1.3.3. It features a different Facebook implementation which hopefully fixes most of the problems reported relating to Facebook. It should be out fairly soon, in the next ten days or so.