[Bug 692358] appsrc deadlock setting the pipeline to NULL state

[GStreamer (bugzilla.gnome.org)]

https://bugzilla.gnome.org/show_bug.cgi?id=692358
  GStreamer | gst-plugins-base | unspecified

Sebastian Dröge <slomo> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |slomo at circular-chaos.org

--- Comment #12 from Sebastian Dröge <slomo at circular-chaos.org> 2013-02-20 11:28:48 UTC ---
(In reply to comment #11)
> Right, so I can reproduce the deadlock with your test case in 0.10, and it's
> probably still present in 1.0.
> 
> I am not sure if your solution is really right.
> 
> I think the problem is ultimately that we allow buffers to be pushed into the
> appsrc even in NULL state, both before start and after shutdown.
> 
> As part of the downward state change, the _unlock() and _unlock_stop()
> functions will be called, which will signal on the GCond. After that, no more
> buffers should be accepted IMHO, thus preventing any blocking after that point.

I agree, that's the behaviour that is consistent with the GStreamer concepts in
general.

-- 
Configure bugmail: https://bugzilla.gnome.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
You are the assignee for the bug.