Comment 13 for bug 385192

It is definitely not solved.

When started with library of ~7K songs Listen uses 100% CPU for a while and when finished drops to normal until I try to play anything. First several seconds playing CPU usage is normal and then no matter what, playing or not, window open or not, all plugins and crossfading disabled or not, listen uses all CPU it can get.
My guess is some internal feature that can't be disabled in preferences gathering some info about current playing track misbehaves.

I strongly suspect cover downloader listen/cover_manager.py or related file because of the last messages Listen sends to stdout before hogging cpu [attached file]

How could I further investigate this bug and provide more useful information?

Behaviour observed in version 0.6.2 and standard Karmic Ubuntu installation.

This bug must be reopened.