Skip to content
Snippets Groups Projects
  1. Oct 30, 2015
  2. Oct 29, 2015
  3. Oct 26, 2015
    • George Kiagiadakis's avatar
      waylandsink: don't advertise the local wl_display context · 450bac6c
      George Kiagiadakis authored
      This wl_display proxy is temporary only until waylandsink goes NULL,
      at which point the connection to the display is disposed. Unfortunately,
      if this is advertised as a GstContext, playbin will cache it and re-feed
      it to the sink when it goes PLAYING again, but the wl_display pointer
      will at that point be invalid and cause a crash.
      
      Another solution to the problem would be to also cache the GstWlDisplay
      object inside the GstContext, which would automatically ref-count
      the display connection, but I see no reason in doing that at the moment,
      as there are no known users of this GstContext outside waylandsink.
      It's probably better to avoid chasing hidden refcounts.
      
      https://bugzilla.gnome.org/show_bug.cgi?id=756567
      450bac6c
  4. Oct 25, 2015
    • André Draszik's avatar
      hlsdemux: don't crash or leak memory on broken master playlist · b1fca495
      André Draszik authored and Tim-Philipp Müller's avatar Tim-Philipp Müller committed
      If a (master) playlist contains a variant list entry without a
      URI then during parsing of the next variant list entry we are
      a) leaking the entry we're currently parsing (new_list), and
      b) free'ing the pointer to the previous list entry (list) without
         updating the pointer.
      
      Hence when then adding the URI for the latest parsed entry, incorrect
      information is stored, as the information is used from 'list' which
      is not valid memory anymore, also leading to crashes.
      
      Fix this by correctly storing the new variant list entry pointer
      as needed.
      
      https://bugzilla.gnome.org/show_bug.cgi?id=756861
      b1fca495
  5. Oct 23, 2015
  6. Oct 20, 2015
  7. Oct 19, 2015
  8. Oct 17, 2015
  9. Oct 15, 2015
    • Edward Hervey's avatar
      hlsdemux: Avoid negative sequence numbers · 2aea4691
      Edward Hervey authored and Edward Hervey's avatar Edward Hervey committed
      For live streams, we want to make sure there's a certain distance
      between the sequence to play and the last (earliest) fragment.
      
      The problem is that it assumes there are at least 3 fragments in
      the playlist, which might not always be the case (like in the case
      of a server restarting and gradually adding fragments).
      
      In order to avoid ending up with negative sequence numbers (which
      will just loop forever), limit the new target sequence number to
      the highest of:
      * either the first sequence number of the playlist (fallback)
      * or 3 fragments from the last one (standard behaviour)
      2aea4691
  10. Oct 11, 2015
  11. Oct 07, 2015
  12. Oct 05, 2015
  13. Oct 02, 2015
Loading