[Gstreamer-bugs] [Bug 115559] Changed - Deadlock with video thread

bugzilla-daemon at widget.gnome.org bugzilla-daemon at widget.gnome.org
Fri Jun 20 06:49:47 PDT 2003


Please do not reply to this email- if you want to comment on the bug, go to the
URL shown below and enter your comments there.

http://bugzilla.gnome.org/show_bug.cgi?id=115559

Changed by newhallibaby at gmx.de.

--- shadow/115559	Fri Jun 20 09:32:49 2003
+++ shadow/115559.tmp.4275	Fri Jun 20 09:49:47 2003
@@ -34,6 +34,26 @@
 Created an attachment (id=17634)
 gdb output of all processes
 
 
 ------- Additional Comments From rbultje at ronald.bitfreak.net  2003-06-20 09:32 -------
 What pipeline are you using exactly? What elements?
+
+------- Additional Comments From newhallibaby at gmx.de  2003-06-20 09:49 -------
+Normal pipeline created via gst_pipeline_new(...) with a filesrc and
+mpegdemux element.
+
+In first thread (called "video_thread") there are: video_input_queue
+(queue), video_decoder (mpeg2dec), video_converter (colorspace),
+video_encoder (my sam_video_encoder codec) and video_output queue.
+
+The second thread (called "audio_thread") contains of:
+audio_input_queue (queue), audio_decoder (mpeg2dec), audio_encoder (my
+sam_audio_encoder codec) and audio_output queue.
+
+The third and last thread has: muxer (my sam_multiplexer codec) and a
+filesink.
+
+That's all. I tried different schedulers but all stop completely
+working after 0,19% up to 1,20% of 700MB transcoded. If I apply a
+gst-mask=0x100 I get sometimes (really only sometime) that queues get
+decoupled! 





More information about the Gstreamer-bugs mailing list