GNOME Bugzilla – Bug 348425
deadlock/hang in gst_system_clock_obtain
Last modified: 2006-11-18 13:34:44 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
This stack trace looks very wrong. Any chance you could capture this hang with a debug log? This was with a video only pipeline?
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.
Can we close this?
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. :-)