| 2006-01-31 20:29:55 |
Darryl Clarke |
bug |
|
|
added bug |
| 2006-02-01 01:50:36 |
Darryl Clarke |
rhythmbox: severity |
Normal |
Critical |
|
| 2006-02-01 01:50:36 |
Darryl Clarke |
rhythmbox: statusexplanation |
|
After roughly 5 hours of playtime:
PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
25235 dclarke 15 0 1028m 102m 16m S 4 10.2 12:21.56 rhythmbox
304 dclarke 15 0 1019m 86m 1252 S 0 8.6 0:00.00 rhythmbox
I am putting this as 'critical' due to the fact that after such playtime my kernel has begun killing processes due to low memory. |
|
| 2006-02-01 16:41:58 |
Phil Bull |
rhythmbox: assignee |
|
desktop-bugs |
|
| 2006-02-01 16:41:58 |
Phil Bull |
rhythmbox: severity |
Critical |
Normal |
|
| 2006-02-01 16:41:58 |
Phil Bull |
rhythmbox: statusexplanation |
After roughly 5 hours of playtime:
PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
25235 dclarke 15 0 1028m 102m 16m S 4 10.2 12:21.56 rhythmbox
304 dclarke 15 0 1019m 86m 1252 S 0 8.6 0:00.00 rhythmbox
I am putting this as 'critical' due to the fact that after such playtime my kernel has begun killing processes due to low memory. |
Thanks for the report.
Does this only happen with rhythmbox, or can it occur with other music players?
You might like to try to profile the memory usage of rhythmbox. Install the 'valgrind' package and run the following command from the terminal (all one line):
valgrind --tool=massif --depth=5 --alloc-fn=g_malloc
--alloc-fn=g_realloc --alloc-fn=g_try_malloc --alloc-fn=g_malloc0
--alloc-fn=g_mem_chunk_alloc rhythmbox
Rhythmbox will be very slow, but let it run for a little while. When you close rhythmbox, you should get a couple of files written to your current directory (called massif something). Open the ps file for a nice graph of memory allocation by the process over time. This *might* shed some light on the problem, I don't know.
Also, I've reduced the severity until this can be confirmed.
Thanks again |
|
| 2006-02-02 08:25:48 |
Phil Bull |
rhythmbox: status |
Unconfirmed |
Needs Info |
|
| 2006-02-02 08:25:48 |
Phil Bull |
rhythmbox: statusexplanation |
Thanks for the report.
Does this only happen with rhythmbox, or can it occur with other music players?
You might like to try to profile the memory usage of rhythmbox. Install the 'valgrind' package and run the following command from the terminal (all one line):
valgrind --tool=massif --depth=5 --alloc-fn=g_malloc
--alloc-fn=g_realloc --alloc-fn=g_try_malloc --alloc-fn=g_malloc0
--alloc-fn=g_mem_chunk_alloc rhythmbox
Rhythmbox will be very slow, but let it run for a little while. When you close rhythmbox, you should get a couple of files written to your current directory (called massif something). Open the ps file for a nice graph of memory allocation by the process over time. This *might* shed some light on the problem, I don't know.
Also, I've reduced the severity until this can be confirmed.
Thanks again |
Give a smaller playlist a try, only about 2000 songs, if possible, and run that for a few hours. It might be a playlist handling bug somewhere.
With beep-media-player, are you using the gstreamer or xine backend? Could you try the xine backend with totem and try to reproduce the problem?
Thanks again |
|
| 2006-02-03 06:15:36 |
Darryl Clarke |
rhythmbox: statusexplanation |
Give a smaller playlist a try, only about 2000 songs, if possible, and run that for a few hours. It might be a playlist handling bug somewhere.
With beep-media-player, are you using the gstreamer or xine backend? Could you try the xine backend with totem and try to reproduce the problem?
Thanks again |
Moving this to a more appropriate package to match an upstream report - and it has come clear that it is not a rhythmbox bug. |
|
| 2006-02-04 19:21:29 |
Phil Bull |
gst-plugins-base0.10: status |
Needs Info |
Confirmed |
|
| 2006-02-04 19:21:29 |
Phil Bull |
gst-plugins-base0.10: statusexplanation |
Moving this to a more appropriate package to match an upstream report - and it has come clear that it is not a rhythmbox bug. |
Some news from upstream:
http://bugzilla.gnome.org/show_bug.cgi?id=329713
Reported as fixed in CVS. |
|
| 2006-02-10 05:58:18 |
Darryl Clarke |
gst-plugins-base0.10: status |
Confirmed |
Fix Released |
|
| 2006-02-10 05:58:18 |
Darryl Clarke |
gst-plugins-base0.10: statusexplanation |
Some news from upstream:
http://bugzilla.gnome.org/show_bug.cgi?id=329713
Reported as fixed in CVS. |
As stated upstream, this fix has made its way in by way of
gstreamer0.10-plugins-base:
Installed: 0.10.3-0ubuntu1 |
|
