[vlc-devel] Another HLS question: vlc_object_alive vs. Close

Rémi Denis-Courmont remi at remlab.net
Wed Jun 6 16:36:57 CEST 2012

This is not news. It was already discussed a few months ago. stream_filter was 
not designed with blocking/network access in mind. And the developers that 
wrote network-based stream filters conveniently ignored the problem. That was 
DASH then HLS.

vlc_object_alive() does not properly solve this issue. And nothing else does 
as of now.

Le mercredi 6 juin 2012 17:07:58 Chris Smowton, vous avez écrit :
> So I had a go at rewriting this to avoid using object_alive, but found
> it impossible with the current asynchronous shutdown mechanism. The
> problem is when shutdown requests happen between one segment download
> and the next; in this case the fresh access_http which is created to
> conduct the second download doesn't inherit the waitpipe status of its
> parent, and as a result it succeeds, potentially taking a long time to
> do so. What's needed is either (a) a custom interrupt callback, like
> that which is called from vlc_object_destroy, allowing me to notify the
> download thread appropriately, or (b) access to the waitpipe function
> from modules, though this latter would be ugly as I'd have to run a
> dedicated thread that just watches the waitpipe and repeats that in a
> different form.

Rémi Denis-Courmont

More information about the vlc-devel mailing list