iTunes process consumes 99% of CPU upon exit

  • Thread starter Thread starter khvatov
  • Start date Start date
K

khvatov

Hi,
After some research I could not find an answer. I have iTunes installed
on my laptop. The use of iTunes does not consume a lot of CPU power,
but when I close the application I can see in Task Manager iTunes
process consumes 99% of CPU. It continues for a while and then stops.

I can't seem to figure out what the problem is? Is it normal?
Alex
 
In (e-mail address removed) had this to say:

My reply is at the bottom of your sent message:
Hi,
After some research I could not find an answer. I have iTunes
installed on my laptop. The use of iTunes does not consume a lot of
CPU power, but when I close the application I can see in Task Manager
iTunes process consumes 99% of CPU. It continues for a while and then
stops.

I can't seem to figure out what the problem is? Is it normal?
Alex
Click to expand...

The problem is, likely, that it's iTunes...

Apple - Support - iTunes:
http://www.apple.com/support/itunes/

Apple - Support - iPod:
http://www.apple.com/support/ipod/

You can get a QT plug-in for JetAudio's free version IIRC.

--
Galen - MS MVP - Windows (Shell/User & IE)
http://dts-l.org/
http://kgiii.info/

"At present I am, as you know, fairly busy, but I propose to devote my
declining years to the composition of a textbook which shall focus the
whole art of detection into one volume." - Sherlock Holmes
 
Hi,
After some research I could not find an answer. I have iTunes installed
on my laptop. The use of iTunes does not consume a lot of CPU power,
but when I close the application I can see in Task Manager iTunes
process consumes 99% of CPU. It continues for a while and then stops.

I can't seem to figure out what the problem is? Is it normal?
Alex
Click to expand...

Yes, it is normal, as it is writing updates to the database. On slower
machines, it used to last more than a minute with a library of 20,000 files. On
my new machine, which has an Athlon 64 X2, and 1GB of RAM, it lasts less than
five seconds. Many similar apps exhibit the same behavior, but Apple hasn't
figured out how to update a database efficiently yet.
 
Back
Top