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):
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 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 fn=g_realloc --alloc- fn=g_try_ malloc --alloc- fn=g_malloc0 fn=g_mem_ chunk_alloc rhythmbox
--alloc-
--alloc-
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