Red Hat Bugzilla – Bug 986612
Memory leak when loading very large playlist
Last modified: 2015-02-17 11:16:34 EST
Description of problem:
I clicked the '+' sign at the bottom left of the Rhythmbox window and then indicated that I wanted to add a new playlist from a file. I specified the .m3u file containing the playlist, which has 1852 songs in it, including some with UTF-8 characters in their names (I don't know if that's relevant). Rhythmbox appeared to load the playlist successfully, i.e., it said that there were 1852 songs loaded, but then it hung and crashed.
Version-Release number of selected component:
runlevel: N 5
Thread no. 1 (7 frames)
#2 g_thread_new at gthread.c:839
#3 rb_uri_handle_recursively_async at rb-file-helpers.c:967
#4 next_uri at rhythmdb-import-job.c:361
#5 _recurse_async_data_free at rb-file-helpers.c:891
#9 g_main_context_iteration at gmain.c:3762
#10 g_application_run at gapplication.c:1623
#11 rb_application_run at rb-application.c:637
Created attachment 776329 [details]
Created attachment 776330 [details]
Created attachment 776331 [details]
Created attachment 776332 [details]
Created attachment 776333 [details]
Created attachment 776334 [details]
Created attachment 776335 [details]
Created attachment 776336 [details]
Created attachment 776337 [details]
Created attachment 776338 [details]
Created attachment 776339 [details]
I figured out more about the problem. I have a memory limit set of 6GB. When I removed the memory limit and logged out and logged back in and tried to load the playlist again in rhythmbox, it worked just fine, but rhythmbox's memory footprint ballooned to *** almost 17GB ***. When I subsequently exited and restarted rhythmbox, it was using 1.6GB of memory.
It appears that there's a memory leak of some sort when Rhythmbox is loading a playlist from a file.
This message is a notice that Fedora 19 is now at end of life. Fedora
has stopped maintaining and issuing updates for Fedora 19. It is
Fedora's policy to close all bug reports from releases that are no
longer maintained. Approximately 4 (four) weeks from now this bug will
be closed as EOL if it remains open with a Fedora 'version' of '19'.
Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version.
Thank you for reporting this issue and we are sorry that we were not
able to fix it before Fedora 19 is end of life. If you would still like
to see this bug fixed and are able to reproduce it against a later version
of Fedora, you are encouraged change the 'version' to a later Fedora
version prior this bug is closed as described in the policy above.
Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.
Fedora 19 changed to end-of-life (EOL) status on 2015-01-06. Fedora 19 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.
If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
Thank you for reporting this bug and we are sorry it could not be fixed.