Rhythmbox makes system hang when importing dir

Bug #15421 reported by Eric Feliksik on 2005-04-12
Affects Status Importance Assigned to Milestone
rhythmbox (Ubuntu)
Sebastien Bacher

Bug Description

I'm running Hoary. I had double entries in rhythmbox, so I decided to remove
them all and import the 'albums' directory again. It contains 18gb of music in
about 3500 files. It took a while, of course, but at a certain point the system
got *very* unresponsive. It turned out the load was raised to about 18 (!), and
memory usage of rhythmbox according to top was 65% (I have 512MB ram and 512MB
swap). After a long time and a lot of patience rhythmbox was killed, or I could
kill it in a terminal.

I repeated this a few times, also after removing ~/.gnome2/rhythmbox/ , but the
problem persists.

I should note that there was a popup to tell me one mp3 could not be imported,
because the stream type could not be detected.... Other mp3's apparently did
work, and I have gstreamer0.8-mad installed.

http://bugzilla.gnome.org/show_bug.cgi?id=307692: http://bugzilla.gnome.org/show_bug.cgi?id=307692

Sebastien Bacher (seb128) wrote :

can you run "rhythmbox -d" and see what happens, on what file it's hanging?

Eric Feliksik (milouny) wrote :

Hey, it took me too long and I threw a mail to the rhythmbox mailinglist.
Someone claimed these bugs represent the same thing:


So I will wait till it's fixed ;) By the way, this is an evil file I could


I guess this can be closed.

Sebastien Bacher (seb128) wrote :

bug fixed, thanks

Eric Feliksik (milouny) wrote :

I upgraded to:
rhythmbox 0.8.8-11ubuntu1
libid3tag0 0.15.1b-5

The 'angelhead.mp3' of http://bugzilla.gnome.org/show_bug.cgi?id=162647 indeed
loads correctly, but my 'test.mp3' still causes the same problem. Can you
confirm this?

I don't know how to fix this, but hereby I reopen this bug.

Sebastien Bacher (seb128) wrote :

right, rhythmbox has some issue on this file, I've opened a bug upstream about
this: http://bugzilla.gnome.org/show_bug.cgi?id=307692

Eric Feliksik (milouny) wrote :

Thank you for sending it upstream.

The problem for me is often that when I send a bug upstream (especially directly
to the project maintainer) I'm told "Use the cvs version or don't report bugs".
Therefore I simply complain at the ubuntu team, which handles things excellent.

Is this the way to go, or do you have an advice for this situation?


Sebastien Bacher (seb128) wrote :

I doubt you get this sort of reply on the GNOME bugzilla, usually they are nice
and ask if you can try with a current version when they don't get the issue (and
Ubuntu packages are uptodate usually with the upstream version). Anyway sending
bugs here works too, we know what versions are used, what patches are used and
if the bug is likely an upstream one.

Eric Feliksik (milouny) wrote :

Ok, that's great. Thanks.

Sebastien Bacher (seb128) wrote :

*** Bug 19351 has been marked as a duplicate of this bug. ***

Sebastien Bacher (seb128) wrote :

This upload fixes the issue:

 gst-plugins0.8 (0.8.10-1ubuntu3) breezy; urgency=low
   * debian/patches/02_gstgnomevfssrc.c.patch:
     - patch from the CVS, fix an issue with ID3v1 tag (Ubuntu: #9114).

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.