GNOME Bugzilla – Bug 737793
hlsdemux: Fix accessing invalidated memory.
Last modified: 2014-10-07 12:22:50 UTC
Created attachment 287611 [details] [review] Patch In gst_hls_demux_get_next_fragment() the next fragment URI gets stored in next_fragment_uri, but the gst_hls_demux_updates_loop() can at any time update the playlist, rendering this string invalid. Therefore, any data (like key, iv, URIs) that is taken from a GstM3U8Client needs to be copied. In addition, accessing the internals of a GstM3U8Client requires locking.
commit c87835a79ff31d8d9fe1f71726fb8d466136c21f Author: Thomas Bluemel <tbluemel@control4.com> Date: Thu Oct 2 10:37:57 2014 -0600 hlsdemux: Fix accessing invalidated memory In gst_hls_demux_get_next_fragment() the next fragment URI gets stored in next_fragment_uri, but the gst_hls_demux_updates_loop() can at any time update the playlist, rendering this string invalid. Therefore, any data (like key, iv, URIs) that is taken from a GstM3U8Client needs to be copied. In addition, accessing the internals of a GstM3U8Client requires locking. https://bugzilla.gnome.org/show_bug.cgi?id=737793