Skip to content
Snippets Groups Projects
  1. Jan 20, 2016
  2. Jan 16, 2016
  3. Jan 15, 2016
  4. Jan 11, 2016
  5. Dec 28, 2015
  6. Dec 23, 2015
  7. Dec 18, 2015
  8. Dec 14, 2015
  9. Dec 11, 2015
  10. Dec 08, 2015
  11. Dec 07, 2015
  12. Dec 01, 2015
  13. Nov 20, 2015
  14. Nov 19, 2015
  15. Nov 17, 2015
  16. Nov 16, 2015
  17. Nov 11, 2015
  18. Nov 10, 2015
  19. Nov 07, 2015
    • Edward Hervey's avatar
      dvbsuboverlay: Don't send flush events · bd8bd094
      Edward Hervey authored and Sebastian Dröge's avatar Sebastian Dröge committed
      It is up to the element handling the seek to send flush events
      downstream, otherwise we end up with a situation where upstream
      would get unexpected GST_FLOW_FLUSHING
      bd8bd094
    • Tim-Philipp Müller's avatar
      assrender: don't send flush events on seeks · dc892d0b
      Tim-Philipp Müller authored and Sebastian Dröge's avatar Sebastian Dröge committed
      It's for the upstream element driving the pipeline to
      handle seeks and send flush events or not, filters
      should not interfere here, otherwise downstream pads
      could be flushing before upstream pads are flushing,
      which can result in GST_FLOW_ERROR being sent instead
      of GST_FLOW_FLUSHING when trying to forward sticky
      events at just the wrong moment.
      dc892d0b
  20. Nov 03, 2015
  21. Oct 30, 2015
  22. Oct 29, 2015
  23. 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
  24. 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
  25. Oct 23, 2015
Loading