Adium

Opened 15 years ago

Closed 15 years ago

Last modified 12 years ago

#2352 closed defect (fixed)

CPU Spiking (lookupd)

Reported by: fire@nexus9.org Owned by: nobody
Milestone: Adium X 1.0 Component: None
Version: Severity: major
Keywords: cpu usage, lookupd, spike, windowserver Cc:
Patch Status:

Description

Adium causes a CPU spike every 10-15 seconds. The processes causing the huge CPU usage are lookupd (80-90%) and windowserver (10-15%). The problem ceases when I log off my AIM account or quit adium. I am using the iTunes scripts for my profile. They could be the source of the problem.

It took several tries, but I managed to catch Adium with some abnormal feedback using the process sampler at the onset of the CPU spike. I also took samples of WindowServer and lookupd. There are also screenshots of the visual CPU monitor I took. They clearly display the problem.

Attachments (5)

AdiumSample.txt (7.7 KB) - added by fire@… 15 years ago.
LookupdSample1.txt (15.5 KB) - added by fire@… 15 years ago.
LookupdSample2.txt (15.4 KB) - added by fire@… 15 years ago.
WindowserverSample.txt (5.7 KB) - added by fire@… 15 years ago.
CPUMonitor.png (16.8 KB) - added by fire@… 15 years ago.

Download all attachments as: .zip

Change History (11)

Changed 15 years ago by fire@…

Attachment: AdiumSample.txt added

Changed 15 years ago by fire@…

Attachment: LookupdSample1.txt added

Changed 15 years ago by fire@…

Attachment: LookupdSample2.txt added

Changed 15 years ago by fire@…

Attachment: WindowserverSample.txt added

Changed 15 years ago by fire@…

Attachment: CPUMonitor.png added

comment:1 Changed 15 years ago by Colin Barrett

priority: highnormal

If you have issues with lookupd locking up, try unlockupd http://www.dshadow.com/software/unlockupd/

My suspicion is that it's your script in there, looking at that sample.

comment:2 Changed 15 years ago by fire@…

When I remove the iTunes scripts from my profile, the spiking stops. It's most certainly related to that.

I was calling the following scripts from my profile (in this order): %_track %_artist %_album %_year

When I called each script individually from a chat, I recieved little baby spikes for each one (still 100%, but not as long as the spikes shown in CPUMonitor.png) -- which makes perfect sense, but is only more evidence that the iTunes scripts are the problem.

comment:3 Changed 15 years ago by fire@…

unlockupd does not solve the problem.

comment:4 Changed 15 years ago by Evan Schoenberg

Those iTunes scripts will all have 0 impact on CPU usage as of 1.0.

comment:5 Changed 15 years ago by Chris Forsythe

Milestone: Adium X 1.0

We're changing from polling to distributed notifications with 1.0, for iTunes integration. It would help if we had a checkbox next to areas that could take itunes info so that users know to remove the iTunes scripts though.

comment:6 Changed 15 years ago by David Smith

Resolution: fixed
Status: newclosed

Closing based on Evan's comments. Tick's suggestion can move to a new ticket.

Note: See TracTickets for help on using tickets.