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 97028 - Rhythmbox crash on GStreamer thread malfunction.
Rhythmbox crash on GStreamer thread malfunction.
Status: VERIFIED INCOMPLETE
Product: GStreamer
Classification: Platform
Component: gstreamer (core)
0.3.3
Other other
: Normal critical
: 0.4.0
Assigned To: GStreamer Maintainers
GStreamer Maintainers
: 97920 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2002-10-28 14:26 UTC by Samuel Stringham
Modified: 2009-08-15 18:40 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
Stack trace for the previous (14.80 KB, text/plain)
2002-11-07 17:21 UTC, Tommi Komulainen
Details
Stack trace for crash with basicwingo scheduler (10.71 KB, text/plain)
2002-11-07 21:22 UTC, Tommi Komulainen
Details

Description Samuel Stringham 2002-10-28 14:21:15 UTC
Package: GStreamer
Severity: normal
Version: 0.3.0.99
Synopsis: Rhythmbox crash on GStreamer thread malfunction.
Bugzilla-Product: GStreamer
Bugzilla-Component: gstreamer (core)
BugBuddy-GnomeVersion: 2.0 (2.1.1)

Description:
Description of Problem:

Random crash, looks like something to do with threading, which I can
help little on.  Looks like it tried to destroy a thread, failed because
the device was busy, and then maybe the return value wasn't checked? 
This is a rhythmbox trace, but I think it has more to do with
GStreamer.



Debugging Information:

Backtrace was generated from '/opt/gnome2/bin/rhythmbox'

[New Thread 1024 (LWP 16587)]
[New Thread 2049 (LWP 16588)]
[New Thread 1026 (LWP 16589)]
[New Thread 2051 (LWP 16590)]
[New Thread 3076 (LWP 16591)]
[New Thread 4101 (LWP 16592)]
0x40c881e9 in __wait4 () from /lib/libc.so.6

Thread 5 (Thread 3076 (LWP 16591))

  • #0 __wait4
    from /lib/libc.so.6
  • #1 __DTOR_END__
    from /lib/libc.so.6
  • #2 waitpid
    at wrapsyscall.c line 173
  • #3 libgnomeui_segv_handle
    at gnome-ui-init.c line 646
  • #4 pthread_sighandler
    at signals.c line 97
  • #5 <signal handler called>
  • #6 g_logv




------- Bug moved to this database by unknown@bugzilla.gnome.org 2002-10-28 09:21 -------

Unknown version unspecified in product GStreamer. Setting version to "0.3.3".
Reassigning to the default owner of the component, gstreamer-maint@bugzilla.gnome.org.

Comment 1 Tommi Komulainen 2002-11-07 17:20:59 UTC
Version: 0.4.2.1

I'm seeing propably the same thing on this SMP.  It's totally random
when the crash occurs, sometimes only minutes, sometimes after hours
of running.  On the console I get:

GThread-ERROR **: file gthread-posix.c: line 228
(g_cond_free_posix_impl): error 'Device or resource busy' during
'pthread_cond_destroy ((pthread_cond_t *) cond)'
aborting...
Xlib: unexpected async reply (sequence 0x296f3)!
Comment 2 Tommi Komulainen 2002-11-07 17:21:25 UTC
Created attachment 12130 [details]
Stack trace for the previous
Comment 3 Samuel Stringham 2002-11-07 21:14:09 UTC
this is 0.4.2 for me, and I also have SMP (dual celeron 366).  Maybe
this is something deeper like a pthread/SMP issue?  (I also submitted
this to rhythmbox as I haven't been able to reproduce it with
gst-player yet.  Hmm . . .)  Also confirming since someone else
reports they can see it:)
Comment 4 Tommi Komulainen 2002-11-07 21:22:01 UTC
Just because I also have dual celeron 366 doesn't mean it's
processors' fault... :)

I'm posting here, because I'm sufficiently certain that rhythmbox has
nothing to do with it.  Now I got a crash with the basicwingo
scheduler.   Output to the console was identical to that in my
previous comment.  Boy is this fun or what :)
Comment 5 Tommi Komulainen 2002-11-07 21:22:33 UTC
Created attachment 12137 [details]
Stack trace for crash with basicwingo scheduler
Comment 6 Olivier Martin 2002-11-08 08:01:12 UTC
*** Bug 97920 has been marked as a duplicate of this bug. ***
Comment 7 Christian Fredrik Kalager Schaller 2003-01-16 14:25:29 UTC
Ok, all thread related issues seems to be related to thread code for
i686 in RH (and probably other i686 optimized glibc versions out there).
glibc in RH8.1 solves this. Putting on needinfo for some days before
closing in case my assumption about the systems involved is mistaken.
Comment 8 Christian Fredrik Kalager Schaller 2003-01-23 13:49:58 UTC
Nothing heard so closing.