Huge performance problem since update

[Lionel Dricot]

I was using the rhythmbox of Intrepid (with the fadeout lock bug).

Yesterday, I've upgraded to 0.11.6svn20081008-0ubuntu4.2 from intrepid-update.

Since then, Rhythmbox and pulseaudio are using together approximately 15% of the CPU. (+/- 10% for RB and 5% for pulseaudio). It was definitely not the case before the update.

More : each time I do "something" on my computer (like changing tabs in my browser, opening a new window or a new gnome-terminal), the sound will become jerky and even stop for half a second.

Note: I've disabled the fadeout/fadein plugin. I've not tested with the plugin enabled.

[Sebastien Bacher (seb128)]

thank you for your bug report, the new version has changes limited to the devices listing and the crossfading option, did you do other updates than the rhythmbox one? the rhythmbox update is not likely to create the issue there

[Lionel Dricot (ploum-deactivatedaccount)]

Well, I didn't updated intrepid for 2 weeks so it means the change should be somewhere in those 2 weeks update.

I didn't changed anything else on this system. No installation, no system configuration.

Maybe it's something external (I've seen on another computer that tracker is becoming a bit crazy those times) but I've reported the bug against RB as it was the one listed by top.

[Sebastien Bacher (seb128)]

could you add your dpkg.log to the bug, it should show what you did update, could also restart your session and try if you still get the issue then?

[Lionel Dricot (ploum-deactivatedaccount)]

the problem still persist heavily after multiple reboot and days.

[Sebastien Bacher (seb128)]

you did upgrade lot of things, could you downgrade rhythmbox and see if that's still an issue? as said the rhythmbox update didn't change a lot and it would be interesting to see if the issue is due to it

[Martin Mai (mrkanister-deactivatedaccount-deactivatedaccount)]

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!