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 348425 - deadlock/hang in gst_system_clock_obtain
deadlock/hang in gst_system_clock_obtain
Status: RESOLVED INCOMPLETE
Product: GStreamer
Classification: Platform
Component: gstreamer (core)
0.10.9
Other Linux
: Normal normal
: git master
Assigned To: GStreamer Maintainers
GStreamer Maintainers
Depends on:
Blocks:
 
 
Reported: 2006-07-23 16:24 UTC by Zaheer Abbas Merali
Modified: 2006-11-18 13:34 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Zaheer Abbas Merali 2006-07-23 16:24:37 UTC 
I got a hang after stopping istanbul with a pipeline of:

oggmux name=mux ! filesink location=/tmp/tmpiw_0uR istximagesrc startx=119 starty=34 endx=710 endy=487 name=videosource ! video/x-raw-rgb,framerate=10/1 ! ffmpegcolorspace ! videoscale method=1 ! video/x-raw-yuv,width=592,height=454,framerate=10/1 ! theoraenc ! queue ! mux. gconfaudiosrc name=audiosource ! audioconvert ! vorbisenc ! queue ! mux.

Stopping involves:
self._vsource.set_state(gst.STATE_NULL)
self._vsource.set_locked_state(True)
if self._asource:
    self._asource.set_state(gst.STATE_NULL)
    self._asource.set_locked_state(True)

This is hard to reproduce....
Backtrace follows:

(gdb) thread apply all bt

+ Trace 69542







Comment 1


Wim Taymans





          2006-07-24 09:10:14 UTC
        



This stack trace looks very wrong. Any chance you could capture this hang with a debug log? This was with a video only pipeline?






Comment 2


Zaheer Abbas Merali





          2006-07-24 09:15:32 UTC
        



It's very difficult to reproduce.  (ie only once have i done so, and i did not have debug logs enabled).

The pipeline has audio and video capture.






Comment 3


Tim-Philipp Müller





          2006-10-12 11:49:46 UTC
        



Can we close this?






Comment 4


André Klapper





          2006-11-18 13:34:44 UTC
        



Closing this bug report as no further information has been provided. Zaheer, please feel free to reopen this bug if you can provide the information asked for. :-)