1. 23 Sep, 2021 1 commit
  2. 22 Sep, 2021 1 commit
  3. 20 Sep, 2021 1 commit
  4. 19 Sep, 2021 3 commits
  5. 13 Sep, 2021 2 commits
  6. 09 Sep, 2021 1 commit
  7. 05 Sep, 2021 1 commit
    • Jan Schmidt's avatar
      multiqueue: Use running time of gap events for wakeups. · 5eba4080
      Jan Schmidt authored
      Use gap events to update the next_time of a queue the same
      as buffers or segment events. Fixes problems where a group
      consisting only of sparse streams primarily driven by
      gap events would stall with a full multiqueue because
      unlinked streams in the group were not being woken to
      push data.
      
      Part-of: <!879>
      5eba4080
  8. 27 Aug, 2021 1 commit
  9. 24 Aug, 2021 1 commit
    • Jan Alexander Steffens's avatar
      pad: Keep IDLE probe hook alive during immediate callback · 148ac71a
      Jan Alexander Steffens authored
      When the probe returns GST_PAD_PROBE_REMOVE and gets called concurrently
      from the streaming thread while we're in the callback here, the hook has
      already been destroyed by the time we've reacquired the object lock.
      Consequently, cleanup_hook gets passed an invalid pointer.
      
      Keep another reference to the hook alive to avoid this situation.
      
      Part-of: <!873>
      148ac71a
  10. 20 Aug, 2021 3 commits
  11. 18 Aug, 2021 3 commits
  12. 13 Aug, 2021 1 commit
  13. 10 Aug, 2021 1 commit
    • Tim-Philipp Müller's avatar
      plugin: load plugins with unknown license strings · bb48c4c9
      Tim-Philipp Müller authored
      We shouldn't fail to load plugins just because we don't
      recognise the license string. It's not our job to validate
      licenses, and the license list is outdated and ambiguous
      anyway.
      
      Also add MPL-2.0 to the list, and fix some defunct license
      URLs in the code comments.
      
      Get rid of the hard-coded skip index, doesn't really buy us
      much versus just skipping with a few strlens, and is harder
      to maintain.
      
      Part-of: <!864>
      bb48c4c9
  14. 03 Aug, 2021 1 commit
  15. 31 Jul, 2021 1 commit
  16. 28 Jul, 2021 2 commits
  17. 26 Jul, 2021 4 commits
  18. 20 Jul, 2021 1 commit
  19. 19 Jul, 2021 2 commits
    • Nirbheek Chauhan's avatar
      gstptpclock: Don't leak the GList · ab6faaee
      Nirbheek Chauhan authored and GStreamer Marge Bot's avatar GStreamer Marge Bot committed
      120 bytes in 5 blocks are definitely lost in loss record 7,615 of 9,510
         at 0x484486F: malloc (vg_replace_malloc.c:380)
         by 0x58A2938: g_malloc (gmem.c:106)
         by 0x58BA1F4: g_slice_alloc (gslice.c:1069)
         by 0x588F059: g_list_prepend (glist.c:335)
         by 0x5B9C5C0: select_best_master_clock (gstptpclock.c:756)
         by 0x5B9CA8E: cleanup_cb (gstptpclock.c:1930)
         by 0x589AD20: g_timeout_dispatch (gmain.c:4889)
         by 0x589A4CE: UnknownInlinedFun (gmain.c:3337)
         by 0x589A4CE: g_main_context_dispatch (gmain.c:4055)
         by 0x58EE4E7: g_main_context_iterate.constprop.0 (gmain.c:4131)
         by 0x5899A92: g_main_loop_run (gmain.c:4329)
         by 0x5B9BA4C: ptp_helper_main (gstptpclock.c:1980)
         by 0x58C8C31: g_thread_proxy (gthread.c:826)
      
      576 bytes in 24 blocks are definitely lost in loss record 8,782 of 9,510
         at 0x484486F: malloc (vg_replace_malloc.c:380)
         by 0x58A2938: g_malloc (gmem.c:106)
         by 0x58BA1F4: g_slice_alloc (gslice.c:1069)
         by 0x588F059: g_list_prepend (glist.c:335)
         by 0x5B9C5C0: select_best_master_clock (gstptpclock.c:756)
         by 0x5B9EFA0: handle_announce_message (gstptpclock.c:934)
         by 0x5B9EFA0: handle_ptp_message (gstptpclock.c:1765)
         by 0x5B9EFA0: have_stdin_data_cb (gstptpclock.c:1851)
         by 0x589A4CE: UnknownInlinedFun (gmain.c:3337)
         by 0x589A4CE: g_main_context_dispatch (gmain.c:4055)
         by 0x58EE4E7: g_main_context_iterate.constprop.0 (gmain.c:4131)
         by 0x5899A92: g_main_loop_run (gmain.c:4329)
         by 0x5B9BA4C: ptp_helper_main (gstptpclock.c:1980)
         by 0x58C8C31: g_thread_proxy (gthread.c:826)
         by 0x5DA4298: start_thread (pthread_create.c:481)
      
      Part-of: <!852>
      ab6faaee
    • Nirbheek Chauhan's avatar
      gstpad: Don't spam INFO when default-chaining a buffer list · 60a7a2e7
      Nirbheek Chauhan authored
      This is being logged for each buffer, so it should not use INFO.
      
      Part-of: <!853>
      60a7a2e7
  20. 15 Jul, 2021 1 commit
    • Stéphane Cerveau's avatar
      gitlab: add bug template · 342c05e7
      Stéphane Cerveau authored
      To clarify what is expected in an issue description and avoid
      issue which is just an usage issue, add a bug template in gitlab.
      
      Part-of: <!836>
      342c05e7
  21. 08 Jul, 2021 1 commit
  22. 05 Jul, 2021 1 commit
    • Edward Hervey's avatar
      gstinfo: Improve usage of libdw for backtraces · 8c08cdf9
      Edward Hervey authored and Edward Hervey's avatar Edward Hervey committed
      When getting backtraces, we were always creating a new Dwfl context and then
      discarding it. The problem with that is that it resulted in having to re-scan a
      lot of information for every single backtrace.
      
      In order to fix that issue, use a global on-demand Dwfl context and use it with
      a lock.
      
      Furthermore, we were scanning the mappings of the
      process (dwfl_linux_proc_report) for *every single step* in the backtrace, and
      that function is horrendously expensive (does sscanf on /proc/PID/maps
      ...). While there is a possibility that new mappings might be available (new
      plugins being loaded for example), we can limit ourselves to just do it once per
      backtrace.
      
      These two modifications speed up the elements_leaks unit test (which traces all
      pads with full backtraces) by a factor of 6.
      
      Partially fixes #567
      
      Part-of: <!504>
      8c08cdf9
  23. 01 Jul, 2021 1 commit
  24. 28 Jun, 2021 1 commit
    • Sebastian Dröge's avatar
      basesink: Post a latency message whenever we're ready to answer the query · ba294415
      Sebastian Dröge authored
      Usually the latency message is only posted whenever latency of an
      element changes but that might be too early as the sinks might not be
      able to query the latency at that point yet.
      
      Similarly adding a new sink should cause latency reconfiguration once
      that new sink is able to report its latency.
      
      This fixes latency configuration in pipelines where webrtcbin is the
      only "sink", i.e. it is used in a sendonly session. Before, the latency
      would always be configured to 0.
      
      Part-of: <!843>
      ba294415
  25. 24 Jun, 2021 1 commit
  26. 22 Jun, 2021 1 commit
  27. 21 Jun, 2021 2 commits
    • Corentin Damman's avatar
      Update COPYING to LGPL 2.1 · d157b23f
      Corentin Damman authored and GStreamer Marge Bot's avatar GStreamer Marge Bot committed
      Part-of: <!835>
      d157b23f
    • Jan Schmidt's avatar
      parse: Don't do delayed property setting for top-level properties. · 7f293614
      Jan Schmidt authored and GStreamer Marge Bot's avatar GStreamer Marge Bot committed
      If a property is supplied to gst-launch-1.0 to set on a property that
      implements GstChildProxy, it would always accept any property name
      and try to set it later. This means that (for example) decodebin
      will accept and not complain about property names that can never exist like:
      
      gst-launch-1.0 videotestsrc ! decodebin NON-EXISTING_PROPERTY=adsfdasf ! fakesink
      
      Instead, only try to do deferred property setting for property names
      that contain the :: separator that indicates it's a setting on a child
      that might appear later.
      
      Part-of: <!832>
      7f293614