Bug 217511

Summary: rhythmbox hang
Product: [Fedora] Fedora Reporter: Joe Orton <jorton>
Component: rhythmboxAssignee: Alexander Larsson <alexl>
Status: CLOSED CURRENTRELEASE QA Contact:
Severity: medium Docs Contact:
Priority: medium    
Version: 6CC: bnocera
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: 0.9.6 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2007-01-30 15:43:31 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
backtrace from hung rhythmbox none

Description Joe Orton 2006-11-28 11:29:42 UTC
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):
rhythmbox-0.9.5-4.fc6.x86_64

Comment 1 Joe Orton 2006-11-28 11:32:30 UTC
Created attachment 142277 [details]
backtrace from hung rhythmbox

The rhythmbox UI is completely unresponsive in this state.

Comment 2 Alexander Larsson 2006-11-28 13:35:22 UTC
Strange. Seems to be in some python code.


Comment 3 Matthias Clasen 2006-11-28 13:42:25 UTC
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 ?

Comment 4 Joe Orton 2006-11-28 13:54:26 UTC
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.

Comment 5 Alexander Larsson 2006-11-28 14:14:21 UTC
Yes, 300x300 -> 1x1
1x1 is probably the size of some hidden widget or something.

Comment 6 Joe Orton 2006-12-05 12:23:22 UTC
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.

Comment 7 Bastien Nocera 2007-01-30 15:43:31 UTC
Yeah, that would be the old gdk-pixbuf 1x1 resizing bug.

Filed against Rhythmbox at:
http://bugzilla.gnome.org/show_bug.cgi?id=343345

Fixed in:
2006-07-09  James Livingston  <doclivingston>

        * 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.