Red Hat Bugzilla – Bug 217511
Last modified: 2007-11-30 17:11:50 EST
Description of problem:
rhythmbox seems to go into an infinite loop occasionally on my box.
Playing MP3s off an NFS mount. I don't know what triggers it. I SEGVed it and
will attach a backtrace.
Version-Release number of selected component (if applicable):
Created attachment 142277 [details]
backtrace from hung rhythmbox
The rhythmbox UI is completely unresponsive in this state.
Strange. Seems to be in some python code.
Look at frame #2. It seems to scale down a pixbuf to a teeny size.
gdk-pixbuf is known to use gobs of memory in this case.
Is your rhythmbox process eating up all memory at this point ?
I didn't notice; the core dump is 190Mb in size. If I SEGV a happily-running
rhythmbox it only comes in at ~100Mb, FWIW.
I may only have started seeing this since enabling the "Art Display" plugin.
Yes, 300x300 -> 1x1
1x1 is probably the size of some hidden widget or something.
This happened again - and it does recover after 5+ minutes of eating CPU - the
resident set size was increasing at a rate of about a meg every 15 seconds or so
during that time, according to top.
Yeah, that would be the old gdk-pixbuf 1x1 resizing bug.
Filed against Rhythmbox at:
2006-07-09 James Livingston <email@example.com>
* plugins/artdisplay/artdisplay/__init__.py: some minor changes to try
to prevent #343345:
- don't ever scale to 1x1, just hide the image in that case
- don't fade when the window is minimised
- use the last-good allocation width, not the current one - as
it sometimes get weird values.
Should be fixed in the current FC6 update.