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 362896 - crash in Rhythmbox Music Player:
crash in Rhythmbox Music Player:
Status: RESOLVED INCOMPLETE
Product: GStreamer
Classification: Platform
Component: dont know
0.10.x
Other All
: High critical
: git master
Assigned To: GStreamer Maintainers
GStreamer Maintainers
: 376790 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2006-10-17 16:23 UTC by Nino Aderri
Modified: 2009-01-19 19:22 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16



Description Nino Aderri 2006-10-17 16:23:47 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: 182169600 vsize: 0 resident: 182169600 share: 0 rss: 36814848 rss_rlim: 0
CPU usage: start_time: 1161101276 rtime: 0 utime: 3023 stime: 0 cutime:2686 cstime: 0 timeout: 337 it_real_value: 0 frequency: 8

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 -1228441936 (LWP 7545)]
[New Thread -1357927520 (LWP 8511)]
[New Thread -1315964000 (LWP 7988)]
[New Thread -1349534816 (LWP 7987)]
[New Thread -1324356704 (LWP 7568)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

Thread 3 (Thread -1315964000 (LWP 7988))

  • #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 __fsetlocking
    from /lib/tls/i686/cmov/libc.so.6
  • #8 free
    from /lib/tls/i686/cmov/libc.so.6
  • #9 g_free
    from /usr/lib/libglib-2.0.so.0
  • #10 gst_buffer_get_type
    from /usr/lib/libgstreamer-0.10.so.0
  • #11 gst_mini_object_unref
    from /usr/lib/libgstreamer-0.10.so.0
  • #12 gst_vorbis_dec_get_type
    from /usr/lib/gstreamer-0.10/libgstvorbis.so
  • #13 gst_pad_alloc_buffer
    from /usr/lib/libgstreamer-0.10.so.0
  • #14 gst_pad_push
    from /usr/lib/libgstreamer-0.10.so.0
  • #15 gst_queue_get_type
    from /usr/lib/gstreamer-0.10/libgstcoreelements.so
  • #16 gst_task_set_lock
    from /usr/lib/libgstreamer-0.10.so.0
  • #17 g_thread_pool_push
    from /usr/lib/libglib-2.0.so.0
  • #18 g_thread_create_full
    from /usr/lib/libglib-2.0.so.0
  • #19 start_thread
    from /lib/tls/i686/cmov/libpthread.so.0
  • #20 clone
    from /lib/tls/i686/cmov/libc.so.6

Comment 1 Alex Lancaster 2006-10-18 03:55:40 UTC
Thanks for taking the time to report this bug.
This bug report isn't very useful because it doesn't describe the bug well. If you have time and can still reproduce the bug, please read http://bugzilla.gnome.org/bug-HOWTO.html and add a description of how to reproduce this bug.

Also that stack trace is missing some elements that will help a lot to solve the problem, so it will be hard for the developers to fix that crash. Can you get us a stack trace with debugging symbols? Please see http://live.gnome.org/GettingTraces for more information on how to do so. Thanks in advance!
Comment 2 André Klapper 2006-11-16 01:13:04 UTC
Closing this bug report as no further information has been provided. Please feel free to reopen this bug if you can provide the information asked for.
Thanks!
Comment 3 Christian Kirbach 2006-11-19 19:56:51 UTC
*** Bug 376790 has been marked as a duplicate of this bug. ***
Comment 4 Christian Kirbach 2006-11-19 19:58:11 UTC
crash in gstreamer, reopening
Comment 5 Tim-Philipp Müller 2006-11-20 20:38:36 UTC
> crash in gstreamer, reopening

The stack traces of these two bugs don't really look related to me, since there are completely different plugins involved here. Neither stack trace has much useful information unfortunately.




Comment 6 Jens Granseuer 2007-01-18 20:37:09 UTC
Bug 395016 and bug 397846 have very similar traces with yet another set of plugins...
Comment 7 Sebastian Dröge (slomo) 2008-05-05 07:31:28 UTC
Can someone still reproduce this crash with latest gstreamer? If so a new backtrace with glib and gstreamer debug symbols installed would help.
Comment 8 Christoph Wurm 2009-01-19 19:22:26 UTC
Closing this bug report as no further information has been provided. Please feel free to reopen this bug if you can provide the information asked for.
Thanks!