GNOME Bugzilla – Bug 337595
Banshee eats 100% CPU suddenly
Last modified: 2007-02-05 21:07:02 UTC
Please describe the problem: After playing some songs, Banshee will suddenly eat 100% CPU in the middle of a song, without any particular action from the user. Steps to reproduce: 1. Open Banshee 2. Play some songs 3. Watch the CPU usage reaching 100% suddenly Actual results: 100% CPU usage Expected results: Normal CPU usage Does this happen every time? Not every time, but quite often Other information:
We need a little more information to nail this down: Does this happen with specific songs? What kind of audio output are you using? Is something else happening/running on your system?
It doesn't happen with specific songs. Nothing I noticed for the moment. I will try to write down information each time it happens. Output is typical, headset plugged on the front panel of my first computer, speakers on the second one. Typical applications are running at the same time: Firefox, Gaim, OpenOffice. But I'm using Dapper (so unstable distro), with Xgl. I will add more information here once I have faced the problem a couple more times.
Moving to the Playback component. Can't fix this if we don't know how to reproduce this though.
I can't find a reason why it's freezing at one moment. It's not always on the same song, but I can't have Banshee running for more than one hour no matter what I listen to. So I guess I can say that I can reproduce it easily, but only on my computer... I will keep on looking for a logical reason.
francois, is this still an issue?
I also get this behavior. You can see the extract from top here. PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND 10729 trevor 25 0 135m 38m 21m R 100 1.9 1:45.31 banshee 10168 trevor 15 0 29156 19m 7700 S 2 0.9 0:17.56 skype 7988 root 15 0 78412 50m 13m S 2 2.5 1:51.00 X Using Banshee 0.10.12 on Gentoo on Dell Inpsiron 6400 2Gig Ram Intel Core Duo 2400 (no fancy 3d desktop though) This happens when I bring up the preferences dialog, I don't need to do anything and the behaviour continues after the dialog is closed.
What versions are you using? We're at 0.11.2 now and a lot of performance work and stability has gone in since 0.10.9.
Oh, just saw 0.10.12 - please try 0.11.2. Also, what plugins do you have enabled, and how many songs are in your library?
0.10.12 is the latest available for gentoo that is not masked. I tried installing the latest, 0.11.1, which is the very lates available for gentoo but masked. unfortunately it failed to compile. In the meantime, I have 662 songs in my library (all mp3) and the following plugins; Autoscrobbler, Metadata Searcher, Notification Area Icon and Multimedia keys (disabled)
I tried diabling all the plugins but cpu usage still went to 100% when I openned the preferences dialog.
I have just built and installed banshee 0.11.2 and the bug I originally saw of the preference dialog immediatly sending CPU to 100% seems fixed, but after only about 2 minutes of playing the CPU once again goes to 100% (on both cpus on my machine)
Having the same problem. Suddenly banshee uses all my CPU for under 1 second but you'll hear the playback engine stopping shortly. It isn't song specific. Sometimes it happens, sometimes not. I tried changing the IOBackend without any success. Also removing all settings from gconf or removing all files at ~/.gnome2/Banshee didn't help. The only thing suprinsing me is that sometimes playing the same song twice the latter works smoothly, perfectly - without any hangs or stops. Banshee 0.11.2 runnning on Gentoo with Kernel 2.6.18, Gnome 2.16.1, GStreamer Core 0.10.8
I have turned off the plugin "Metadata searcher". Since this time I have no 100% CPU and no stops anymore.
Component should be changed to metadata. I suppose if the component is metadata, the severity would be worthy of an increase. Stephan, could you report if this still occurs with the SVN version? SVN includes some big changes to the metadata services stuff.
Hi Josiah, I cannot tell how well the SVN version works but Banshee 0.11.5 does it :) Good work. No hangs or jumps while playing songs anymore.
Credit goes to abock. I believe he is responsible for the metadata changes.