1. 11 Jun, 2019 4 commits
  2. 06 Jun, 2019 2 commits
  3. 05 Jun, 2019 5 commits
  4. 04 Jun, 2019 3 commits
    • Nicolas Dufresne's avatar
      supp: Ignore leaks caused by shout/sethostent · f227f659
      Nicolas Dufresne authored
      sethostent() seems to be using a global state and we endup with leaks from
      that API when called through shout_init(). We had the option to only
      ignore the shout case, but the impression is that if we have shout and
      another sethostend user, as it's a global state, we may endup with a
      different stack trace for the same leak. So in the end, we just ignore
      memory allocated by sethostent in general.
      f227f659
    • Thibault Saunier's avatar
    • Nicolas Dufresne's avatar
      rtpssrcdemux: Avoid taking streamlock out-of-band · f7c712d0
      Nicolas Dufresne authored
      In this change we now protect the internal srcpads list using the
      stream lock and limit usage of the internal stream lock to
      preventing data flowing on the other src pad type while creating
      and signalling the new pad.
      
      This fixes a deadlock with RTPBin shutdown lock. These two locks would
      end up being taken in two different order, which caused a deadlock. More
      generally, we should not rely on a streamlock when handling out-of-band
      data, so as a side effect, we should not take a stream lock when
      iterating internal links.
      f7c712d0
  5. 03 Jun, 2019 5 commits
  6. 29 May, 2019 4 commits
  7. 28 May, 2019 2 commits
  8. 27 May, 2019 1 commit
  9. 26 May, 2019 1 commit
  10. 25 May, 2019 4 commits
  11. 24 May, 2019 1 commit
  12. 23 May, 2019 1 commit
  13. 22 May, 2019 1 commit
  14. 17 May, 2019 1 commit
    • Nicolas Dufresne's avatar
      rtpsession: Always keep at least one NACK on early RTCP · 947a37f3
      Nicolas Dufresne authored
      We recently added code to remove outdate NACK to avoid using bandwidth
      for packet that have no chance of arriving on time. Though, this had a
      side effect, which is that it was to get an early RTCP packet with no
      feedback into it. This was pretty useless but also had a side effect,
      which is that the RTX RTT value would never be updated. So we we stared
      having late RTX request due to high RTT, we'd never manage to recover.
      
      This fixes the regression by making sure we keep at least one NACK in
      this situation. This is really light on the bandwidth and allow for
      quick recover after the RTT have spiked higher then the jitterbuffer
      capacity.
      947a37f3
  15. 16 May, 2019 2 commits
  16. 13 May, 2019 3 commits