1. 07 Jun, 2020 2 commits
  2. 06 Jun, 2020 2 commits
    • Jan Schmidt's avatar
      baseparse: Fix upstream read caching · 177d0fa1
      Jan Schmidt authored
      When running in pull mode (for e.g. mp3 reading),
      baseparse currently reads 64KB from upstream, then mp3parse
      consumes typically around 417/418 bytes of it. Then
      on the next loop, it will read a full fresh 64KB again,
      which is a big waste.
      Fix the read loop to use the available cache buffer first
      before going for more data, until the cache drops to < 1KB.
      Fixes #518
    • Jan Schmidt's avatar
      baseparse: Fix typo · 0f91868e
      Jan Schmidt authored
  3. 04 Jun, 2020 2 commits
  4. 14 Mar, 2020 1 commit
  5. 13 Mar, 2020 2 commits
  6. 26 Feb, 2020 1 commit
  7. 15 Feb, 2020 2 commits
  8. 14 Feb, 2020 1 commit
    • Sebastian Dröge's avatar
      bus: Make setting/replacing/clearing the sync handler thread-safe · a1c0ca3a
      Sebastian Dröge authored
      Previously we would use the object lock only for storing the sync
      handler and its user_data in a local variable, then unlock it and only
      then call the sync handler. Between unlocking and calling the sync
      handler it might be unset and the user_data be freed, causing it to be
      called with a freed pointer.
      To prevent this add a refcounting wrapper struct around the sync
      handler, hold the object lock while retrieving it and increasing the
      reference count and only actually free it once the reference count
      reaches zero.
      As a side-effect we can now also allow to actually replace the sync
      handler. Previously it was only allowed to clear it after initially
      setting it according to the docs, but the code still allowed to clear it
      and then set a different one.
      Fixes #506
  9. 05 Feb, 2020 1 commit
  10. 09 Jan, 2020 1 commit
  11. 05 Dec, 2019 2 commits
  12. 03 Dec, 2019 4 commits
  13. 28 Nov, 2019 1 commit
  14. 05 Nov, 2019 1 commit
    • Víctor Manuel Jáquez Leal's avatar
      gst/parse: define pure-parser depending on bison version · 77141834
      Víctor Manuel Jáquez Leal authored
      After release bison 2.5 the declaration %pure-parser was deprecated
      in favor of %define api.pure
      Nonetheless, until bison 3.4, the declaration was treated as backward
      compatibility, but now bison shows a warning:
        warning: deprecated directive, use ‘%define api.pure’
      The patch's approach is to handle both directives according with the
      used bison's version, by string replacement at source configuration
  15. 26 Oct, 2019 3 commits
  16. 24 Oct, 2019 1 commit
  17. 01 Oct, 2019 3 commits
  18. 23 Sep, 2019 3 commits
  19. 14 Sep, 2019 3 commits
  20. 08 Sep, 2019 3 commits
  21. 03 Sep, 2019 1 commit
    • Nicolas Dufresne's avatar
      bin: Fix minor race when adding to a bin · 94ba1cea
      Nicolas Dufresne authored
      This patch simply add a null check around a case where a child may have
      been unparented concurrently to the deep_add_remove operation. This was
      found by accident in the form of an "IS_GST_OBJECT" assertion, but had
      no other known side effect in that test.