GNOME Bugzilla – Bug 606881
Unreleased mutex lock
Last modified: 2010-08-06 20:26:03 UTC
I'm using Rythmbox on Ubuntu 9.10 Kermic with version 0.12.5-0ubuntu5. After some time of working application hungs and uses 100% processor time ('top' result): 28421 lmovsesj 20 0 246m 49m 22m S 100 2.5 89:43.61 rhythmbox strace on it shows the following results: $ sudo strace -p 28421 Process 28421 attached - interrupt to quit futex(0xb5fc7c90, FUTEX_WAIT_PRIVATE, 2, NULL If I attached with gdb, I see the following backtrace (first 10 frames):
+ Trace 220065
Helps only Rhythmbox reboot.
Please provide a full backtrace for all threads.
Get the same hangs of rhythmbox, also on ubuntu 9.10 karmic, having installed the linux-backports-modules-karmic backport packages. (gdb) thread apply all bt
+ Trace 220468
Your backtrace is missing debug symbols for rhythmbox, glib, and half of gstreamer (?), and it seems to be using both alsa and pulseaudio in the same process, which is pretty weird. What output do you get from 'gconftool-2 -g /system/gstreamer/0.10/default/musicaudiosink' ?
(In reply to comment #3) > Your backtrace is missing debug symbols for rhythmbox, glib, and half of > gstreamer (?), Well, that old problem. Even though I do have debug packages installed and those non-stripped libraries are installed and present in /usr/lib/debug/..., gdb does not pick them up automatically. When I use add-symbol-file for libglib, for instance, it would show me symbols in the backtrace for some function calls and some not, i.e. show those ??? > and it seems to be using both alsa and pulseaudio in the same > process, which is pretty weird. What output do you get from 'gconftool-2 -g > /system/gstreamer/0.10/default/musicaudiosink' ? alsasink
(In reply to comment #3) > Your backtrace is missing debug symbols for rhythmbox, glib, and half of > gstreamer (?), and it seems to be using both alsa and pulseaudio in the same > process, which is pretty weird. What output do you get from 'gconftool-2 -g > /system/gstreamer/0.10/default/musicaudiosink' ? I was using firefox at the same time, which according to audio preferences, was using the alsa plugin.
That sounds like a problem with your version of gdb or with the debug packages. It may also have something to do with mixing your own builds of libraries with the system libraries. Try changing that gconf key to 'autoaudiosink'.
(In reply to comment #4) > (In reply to comment #3) > What output do you get from 'gconftool-2 -g ... > > /system/gstreamer/0.10/default/musicaudiosink' ? > > alsasink Followed http://pulseaudio.org/wiki/PerfectSetup#Audacious to switch from alsa to pulseaudio: gconftool -t string --set /system/gstreamer/0.10/default/audiosink pulsesink gconftool -t string --set /system/gstreamer/0.10/default/audiosrc pulsesrc Maybe that helps.
(In reply to comment #6) > That sounds like a problem with your version of gdb or with the debug packages. > It may also have something to do with mixing your own builds of libraries with > the system libraries. > > Try changing that gconf key to 'autoaudiosink'. Ok. done.
And is this still an issue?
(In reply to comment #9) > And is this still an issue? I built and now run the latest version of rhythmbox, 0.13, on ubuntu 9.10, karmic, and did not have hangs lately, though I haven't used the app to often, lately. But I still get those crashes intermittently when I use the mouse wheel to change volume or to backtrack/advance the track being played.
(In reply to comment #9) > And is this still an issue? Now I'm using Rhythmbox 0.12.8-0ubuntu7 on Ubuntu 10.04.1 and don't have this problem.
Closing as OBSOLETE as per last comment.