Bug 361681 – crash in Rhythmbox Music Player:

After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.

Bug 361681 - crash in Rhythmbox Music Player:


Summary:	crash in Rhythmbox Music Player:


Status:	RESOLVED OBSOLETE

Product:	GStreamer
Classification:	Platform
Component:	gstreamer (core)
Version:	0.10.10
Hardware:	Other All

Importance:	High critical
Target Milestone:	NONE
Assigned To:	GStreamer Maintainers
QA Contact:	GStreamer Maintainers

URL:
Whiteboard:

Duplicates:	365893 367912 369393 369940 377553 377914 384124 386972 386988 388503 395216 395959 396055 396582 399369 404531 406025 408556 408756 411468 415613 417201 418710 418901 420180 420852 422309 422354 425044 429031 440149 467283 470062 474793 504008 (view as bug list)
Depends on:
Blocks:

Reported:	2006-10-12 11:44 UTC by panote_saechiew
Modified:	2009-02-03 13:57 UTC

See Also:
GNOME target:	---
GNOME version:	2.15/2.16

Attachments
stack trace (331.56 KB, text/plain) 2006-12-11 14:15 UTC, mathias	Details

Description panote_saechiew 2006-10-12 11:44:01 UTC

What were you doing when the application crashed?



Distribution: Ubuntu 6.10 (edgy)
Gnome Release: 2.16.1 2006-10-02 (Ubuntu)
BugBuddy Version: 2.16.0

Memory status: size: 188997632 vsize: 0 resident: 188997632 share: 0 rss: 17956864 rss_rlim: 0
CPU usage: start_time: 1160647891 rtime: 0 utime: 83000 stime: 0 cutime:80556 cstime: 0 timeout: 2444 it_real_value: 0 frequency: 7

Backtrace was generated from '/usr/bin/rhythmbox'

(no debugging symbols found)
Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1228457792 (LWP 5182)]
[New Thread -1385636960 (LWP 8137)]
[New Thread -1338090592 (LWP 8136)]
[New Thread -1368851552 (LWP 8135)]
[New Thread -1354876000 (LWP 8134)]
[New Thread -1346483296 (LWP 8128)]
[New Thread -1320055904 (LWP 8127)]
[New Thread -1329697888 (LWP 8126)]
[New Thread -1377244256 (LWP 5489)]
[New Thread -1311663200 (LWP 5208)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

+ Trace 75970

Thread 3 (Thread -1338090592 (LWP 8136))

#0 __kernel_vsyscall
#1 __waitpid_nocancel
from /lib/tls/i686/cmov/libpthread.so.0
#2 gnome_gtk_module_info_get
from /usr/lib/libgnomeui-2.so.0
#3 <signal handler called>
#4 __kernel_vsyscall
#5 raise
from /lib/tls/i686/cmov/libc.so.6
#6 abort
from /lib/tls/i686/cmov/libc.so.6
#7 g_logv
from /usr/lib/libglib-2.0.so.0
#8 g_log
from /usr/lib/libglib-2.0.so.0
#9 ??
from /usr/lib/libgthread-2.0.so.0
#10 ??
from /usr/lib/libgthread-2.0.so.0
#11 ??
#12 ??
from /usr/lib/libgthread-2.0.so.0
#13 ??
from /usr/lib/libgthread-2.0.so.0
#14 ??
#15 ??
from /usr/lib/libgthread-2.0.so.0
#16 _nl_default_dirname
from /lib/tls/i686/cmov/libc.so.6
#17 ??
from /usr/lib/libgthread-2.0.so.0
#18 ??
from /usr/lib/libgstaudio-0.10.so.0
#19 ??
#20 ??
#21 gst_audio_sink_get_type
from /usr/lib/libgstaudio-0.10.so.0
#22 gst_audio_sink_get_type
from /usr/lib/libgstaudio-0.10.so.0
#23 g_object_unref
from /usr/lib/libgobject-2.0.so.0
#24 gst_object_unref
from /usr/lib/libgstreamer-0.10.so.0
#25 gst_object_unparent
from /usr/lib/libgstreamer-0.10.so.0
#26 gst_base_audio_sink_get_type
from /usr/lib/libgstaudio-0.10.so.0
#27 ??
from /usr/lib/gstreamer-0.10/libgstalsa.so
#28 ??
#29 ??
#30 ??
#31 ??
from /usr/lib/libgobject-2.0.so.0
#32 ??
from /usr/lib/gstreamer-0.10/libgstalsa.so
#33 ??
from /usr/lib/libgobject-2.0.so.0
#34 ??
#35 g_object_unref
from /usr/lib/libgobject-2.0.so.0
#36 g_object_unref
from /usr/lib/libgobject-2.0.so.0
#37 gst_object_unref
from /usr/lib/libgstreamer-0.10.so.0
#38 gst_bin_add
from /usr/lib/libgstreamer-0.10.so.0
#39 gst_bin_remove
from /usr/lib/libgstreamer-0.10.so.0
#40 gst_bin_add
from /usr/lib/libgstreamer-0.10.so.0
#41 g_object_unref
from /usr/lib/libgobject-2.0.so.0
#42 gst_object_unref
from /usr/lib/libgstreamer-0.10.so.0
#43 gst_object_replace
from /usr/lib/libgstreamer-0.10.so.0
#44 gst_bin_add
from /usr/lib/libgstreamer-0.10.so.0
#45 gst_element_provide_clock
from /usr/lib/libgstreamer-0.10.so.0
#46 gst_bin_add
from /usr/lib/libgstreamer-0.10.so.0
#47 gst_element_provide_clock
from /usr/lib/libgstreamer-0.10.so.0
#48 gst_bin_add
from /usr/lib/libgstreamer-0.10.so.0
#49 gst_pipeline_use_clock
from /usr/lib/libgstreamer-0.10.so.0
#50 gst_element_provide_clock
from /usr/lib/libgstreamer-0.10.so.0
#51 gst_pipeline_set_new_stream_time
from /usr/lib/libgstreamer-0.10.so.0
#52 gst_play_base_bin_get_type
from /usr/lib/gstreamer-0.10/libgstplaybin.so
#53 ??
from /usr/lib/gstreamer-0.10/libgstplaybin.so
#54 ??
#55 ??
#56 ??
#57 gst_element_continue_state
from /usr/lib/libgstreamer-0.10.so.0
#58 gst_element_continue_state
from /usr/lib/libgstreamer-0.10.so.0
#59 gst_bin_add
from /usr/lib/libgstreamer-0.10.so.0
#60 gst_bin_add
from /usr/lib/libgstreamer-0.10.so.0
#61 g_thread_pool_push
from /usr/lib/libglib-2.0.so.0
#62 g_thread_create_full
from /usr/lib/libglib-2.0.so.0
#63 start_thread
from /lib/tls/i686/cmov/libpthread.so.0
#64 clone
from /lib/tls/i686/cmov/libc.so.6

Comment 1 Alex Lancaster 2006-10-12 11:58:20 UTC

Thanks for the bug report. Unfortunately, that stack trace is not very useful in determining the cause of the crash. Can you get us one with debugging symbols? Please see http://live.gnome.org/GettingTraces for more information on how to do so.

Also please describe what you were doing at the time of the crash, and since the crash happened in gstreamer, which versions of gstreamer and gstreamer plugins you were using.

Comment 2 Karsten Bräckelmann 2006-10-27 18:46:09 UTC

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

Comment 3 Alex Lancaster 2006-10-30 21:10:28 UTC

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

Comment 4 Fabio Bonelli 2006-11-02 15:13:47 UTC

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

Comment 5 Alex Lancaster 2006-11-03 11:44:23 UTC

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

Comment 6 Jan Arne Petersen 2006-11-22 00:05:47 UTC

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

Comment 7 James "Doc" Livingston 2006-12-10 00:32:18 UTC

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

Comment 8 mathias 2006-12-11 14:15:35 UTC

Created attachment 78132 [details]
stack trace

Comment 9 mathias 2006-12-11 14:19:26 UTC

The stack trace was too big for a comment so I added it as an attachment.

Ere are the assertions made by the software before the bug.

** (rhythmbox:8075): CRITICAL **: Resources for ring buffer 0x2aaac8dc4e50
still acquired

GThread-ERROR **: file gthread-posix.c: line 250 (): error 'Périphérique ou
ressource occupé' during 'pthread_cond_destroy ((pthread_cond_t *) cond)'
aborting...

Comment 10 Alex Lancaster 2006-12-11 14:23:42 UTC

The stack trace looks weird and doesn't look like it crashes anywhere in rhythmbox (there are only rb_ or rhythmdb_ function calls at the beginning of the trace), what versions of gstreamer and the gstreamer plugins are you using?

Did you run "thread apply all bt" as described in:

http://live.gnome.org/GettingTraces/Details

Comment 11 Alex Lancaster 2006-12-18 06:14:00 UTC

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

Comment 12 André Klapper 2006-12-22 20:49:28 UTC

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

Comment 13 André Klapper 2006-12-22 20:49:44 UTC

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

Comment 14 mathias 2006-12-22 22:11:36 UTC

The problem is that, with gdb attached to the process, the program is not crashing.
I suppose that it's because the track are skipped much more slowly than without gdb.

So my stack trace was obtained with just the debug package installed and the output of bug buddy.

Comment 15 Alex Lancaster 2006-12-23 22:11:25 UTC

Switching back to unconfirmed, hopefully the main developers will have an idea of what's going on here.

Comment 16 Alex Lancaster 2006-12-23 22:12:17 UTC

(In reply to comment #14)

> So my stack trace was obtained with just the debug package installed and the
> output of bug buddy.

Can you report the versions of gstreamer and the various gstreamer plugins you have?

Comment 17 Jonathan Matthew 2006-12-23 22:20:11 UTC

It looks like you're using a version of gstreamer from before bug 323874 was fixed.  You should be able to find packages for later versions for ubuntu edgy, and upgrading to those would be a good first step in solving this.

Comment 18 mathias 2006-12-23 22:33:36 UTC

I use gstreamer and all the plugin (base, base-apps and good) in version 0.10.

I don't known from when is my version of gstreamer, but according to synaptic (with the ubuntu 6.10 amd64 repository), my system is up to date.

Comment 19 Alex Lancaster 2006-12-23 22:36:19 UTC

(In reply to comment #18)
> I use gstreamer and all the plugin (base, base-apps and good) in version 0.10.

Thanks, but we need to know the *exact* version (including the minor release number), e.g. on my system I have:

$ rpm -qa|grep gstreamer
gstreamer-tools-0.10.10-2.fc6
gstreamer-devel-0.10.10-2.fc6
gstreamer-plugins-good-devel-0.10.4-1.fc6
gstreamer-plugins-ugly-0.10.4-3.lvn6
gstreamer-plugins-base-0.10.10-1.fc6
gstreamer-0.10.10-2.fc6
gstreamer-plugins-base-devel-0.10.10-1.fc6
gstreamer-plugins-ugly-devel-0.10.4-3.lvn6
gstreamer-plugins-good-0.10.4-1.fc6
gstreamer-python-0.10.6-1.fc6
gstreamer-ffmpeg-0.10.2-0.3.20061108.lvn6

Comment 20 mathias 2006-12-23 22:51:48 UTC

gstreamer0.10-alsa                         0.10.10-1ubuntu1                  gstreamer0.10-esd                          0.10.4-0ubuntu3                   gstreamer0.10-ffmpeg                       0.10.1-2ubuntu1                   gstreamer0.10-fluendo-mp3                  0.10.2.debian-1                   gstreamer0.10-fluendo-mpegdemux            0.10.4-0ubuntu1                   gstreamer0.10-gl                           0.10.3+cvs20060918-0ubuntu1       gstreamer0.10-gnomevfs                     0.10.10-1ubuntu1                  gstreamer0.10-plugins-base                 0.10.10-1ubuntu1                  gstreamer0.10-plugins-base-apps            0.10.10-1ubuntu1                  gstreamer0.10-plugins-good                 0.10.4-0ubuntu3                   gstreamer0.10-tools                        0.10.10-1ubuntu2                  gstreamer0.10-x                            0.10.10-1ubuntu1                  ibgstreamer-plugins-base0.10-0            0.10.10-1ubuntu1                  libgstreamer0.10-0                         0.10.10-1ubuntu2                  totem-gstreamer                            2.16.2-0ubuntu2

Comment 21 Alex Lancaster 2006-12-28 00:35:38 UTC

Can you still duplicate this bug?

Comment 22 mathias 2006-12-28 14:52:07 UTC

yes, I can.

Although, there is a little difference with what I described in bug 377553 : before crashing, the windows is not going black & white (or whatever are the "non-responding" colours) and colourful again (as it used to).
If I skip track for about 20 seconds, when I release the alt + right keys, the tracks are skipped for about 30 other seconds, and after that the windows stop responding (it is not re-paint for example) and it is eventually closed.

Comment 23 Alex Lancaster 2006-12-28 15:15:19 UTC

I think the skipping problem is a gstreamer bug, I'm going to switch products.  Feel free to reassign it back to rhythmbox if it turns out not to be a gstreamer bug.

Comment 24 Alex Lancaster 2007-01-11 02:26:17 UTC

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

Comment 25 Tim-Philipp Müller 2007-01-11 09:27:21 UTC

Mathias: so, let me get this right:

With the GStreamer versions mentioned in comment #20 ...

 - you still get the "CRITICAL **: Resources for ring buffer xyz still acquired", or not?

 - you get a new problem: when switching tracks very quickly:
   the sound starts 'skipping' and the window starts 'freezing'
   (ie does not redraw when you move it or minimize/maximise it)?

Comment 26 Bryce Harrington 2007-01-16 01:02:36 UTC

I think this may be the same as the following Ubuntu bug:

  https://bugs.launchpad.net/ubuntu/+source/rhythmbox/+bug/73587

Was able to reproduce the crash on 0.9.7-ubuntu4 compiled from source, with the following backtrace. Steps to reproduce:

1. Restart X11 (ctrl-alt-bksp)
2. From gnome-terminal, run application in gdb
3. Click on 'Radio' in Sources list
4. Doubleclick on a radio station (I clicked on http://radioparadise.steadyhost.com:8002)
5. Displays "pause" symbol next to URL, and segfaults

Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 47580512691856 (LWP 30690)]
0x00002b4630b21fd0 in g_main_context_check () from /usr/lib/libglib-2.0.so.0

(gdb) thread apply all bt

+ Trace 102565

Thread 6 (Thread 1082132800 (LWP 30702))

#0 __lll_mutex_lock_wait
from /lib/libpthread.so.0
#1 _L_mutex_lock_53
from /lib/libpthread.so.0
#2 pthread_mutex_lock
from /lib/libpthread.so.0
#3 ??
from /usr/lib/libglib-2.0.so.0
#4 ??
from /usr/lib/libORBit-2.so.0
#5 link_watch_move_io
from /usr/lib/libORBit-2.so.0
#6 link_servers_move_io_T
from /usr/lib/libORBit-2.so.0
#7 ??
from /usr/lib/libORBit-2.so.0
#8 link_exec_command
from /usr/lib/libORBit-2.so.0
#9 link_set_io_thread
from /usr/lib/libORBit-2.so.0
#10 ORBit_small_invoke_stub
from /usr/lib/libORBit-2.so.0
#11 ConfigDatabase3_add_listener_with_properties
from /usr/lib/libgconf-2.so.4
#12 gconf_engine_notify_add
from /usr/lib/libgconf-2.so.4
#13 gconf_client_add_dir
from /usr/lib/libgconf-2.so.4
#14 ??
from /usr/lib/gstreamer-0.10/libgstgconfelements.so
#15 g_type_create_instance
#16 ??
from /usr/lib/libgobject-2.0.so.0
#17 g_object_newv
from /usr/lib/libgobject-2.0.so.0
#18 g_object_new_valist
from /usr/lib/libgobject-2.0.so.0
#19 g_object_new
from /usr/lib/libgobject-2.0.so.0
#20 gst_element_factory_create
at gstelementfactory.c line 381
#21 gst_element_factory_make
at gstelementfactory.c line 450
#22 rb_player_gst_open
at rb-player-gst.c line 609
#23 rb_shell_player_open_playlist_url
at rb-shell-player.c line 580
#24 open_location_thread
at rb-shell-player.c line 1124
#25 ??
from /usr/lib/libglib-2.0.so.0
#26 start_thread
from /lib/libpthread.so.0
#27 clone
from /lib/libc.so.6
#28 ??

Thread 1 (Thread 47580512691856 (LWP 30690))

#0 g_main_context_check
from /usr/lib/libglib-2.0.so.0
#1 ??
from /usr/lib/libglib-2.0.so.0
#2 g_main_loop_run
from /usr/lib/libglib-2.0.so.0
#3 IA__gtk_main
at gtkmain.c line 1171
#4 main
at main.c line 384

Comment 27 André Klapper 2007-01-17 01:00:58 UTC

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

Comment 28 Alex Lancaster 2007-01-23 12:16:03 UTC

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

Comment 29 Alex Lancaster 2007-02-05 12:25:06 UTC

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

Comment 30 André Klapper 2007-02-09 15:54:04 UTC

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

Comment 31 André Klapper 2007-02-09 15:54:13 UTC

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

Comment 32 André Klapper 2007-02-09 15:54:19 UTC

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

Comment 33 Alex Lancaster 2007-02-16 15:09:36 UTC

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

Comment 34 James "Doc" Livingston 2007-02-17 11:55:57 UTC

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

Comment 35 James "Doc" Livingston 2007-02-24 11:53:02 UTC

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

Comment 36 Alex Lancaster 2007-03-07 07:53:09 UTC

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

Comment 37 Alex Lancaster 2007-03-07 07:54:20 UTC

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

Comment 38 Alex Lancaster 2007-03-07 07:56:14 UTC

Can somebody run the test suggested by Tim in comment #25 and report back here?

Comment 39 James "Doc" Livingston 2007-03-12 07:31:33 UTC

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

Comment 40 Alex Lancaster 2007-03-15 23:40:07 UTC

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

Comment 41 darkspider04 2007-03-16 02:58:03 UTC

El error fue provocado por intentar reproducir varias (más de 50) canciones simultaneamente.

sorry but my english is so basic.

Comment 42 Alex Lancaster 2007-03-20 09:07:45 UTC

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

Comment 43 James "Doc" Livingston 2007-03-21 06:46:31 UTC

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

Comment 44 Alex Lancaster 2007-03-26 03:17:21 UTC

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

Comment 45 Alex Lancaster 2007-03-26 03:17:49 UTC

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

Comment 46 Tim-Philipp Müller 2007-03-30 11:31:32 UTC

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

Comment 47 Philip Withnall 2007-04-03 15:04:19 UTC

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

Comment 48 Philip Withnall 2007-04-12 16:01:30 UTC

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

Comment 49 James "Doc" Livingston 2007-05-25 12:14:40 UTC

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

Comment 50 Philip Withnall 2007-08-16 21:44:27 UTC

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

Comment 51 palfrey 2007-08-27 12:25:23 UTC

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

Comment 52 palfrey 2007-09-24 16:50:44 UTC

Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find.


*** This bug has been marked as a duplicate of 474793 ***

Comment 53 palfrey 2007-09-24 16:51:34 UTC

Sorry about the bug spam. Should be the other way around... Bug 474793 is a duplicate of this one.

Comment 54 palfrey 2007-09-24 16:52:17 UTC

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

Comment 55 Baptiste Mille-Mathias 2007-12-17 08:53:30 UTC

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

Comment 56 Tim-Philipp Müller 2009-02-03 13:57:26 UTC

I've seen this warning before, but I think this got fixed ages ago. Also, no new dupes for a long time. If anyone can still reproduce this with an up-to-date GStreamer core/base, please re-open or (better) file a new bug.