pulsesrc fails to start up
Submitted by David Woodhouse
Link to original bug (#795374)
Description
Using a Pidgin/Farstream pipeline I occasionally see pulsesrc failing to start up. It seems timing-related.
0:00:05.967852418 23118 0x2e41630 INFO basesrc gstbasesrc.c:2739:gst_base_src_loop:<pulsesrc0>
pausing after gst_base_src_get_range() = flushing
0:00:05.967864004 23118 0x2e41630 INFO task gsttask.c:316:gst_task_func:pulsesrc0:src Task going to paused
Working call log at http://david.woodhou.se/fscall-working and
http://david.woodhou.se/fscall-working-graph.svg
Failing call log at http://david.woodhou.se/fscall-silent and
http://david.woodhou.se/fscall-silent-graph.svg
In the working call, the first sample from pulsesrc seems to happen earlier, and it all works fine. In the failing call, we see the above messages. And nothing ever comes out of the pulsesrc again.
<thaytan>
dwmw2_gone, it's not trying to push the samples downstream yet then though - it's just trying to create the first buffer
<thaytan>
it doesn't get as far as trying to push it
<thaytan>
so seems more like a startup race in pulsesrc
Version: 1.8.3