Skip to content
Snippets Groups Projects
  1. Oct 21, 2020
  2. Oct 20, 2020
  3. Oct 16, 2020
  4. Sep 29, 2020
  5. Sep 28, 2020
  6. Sep 25, 2020
  7. Sep 24, 2020
    • Matthew Waters's avatar
      dtls/connection: fix EOF handling with openssl 1.1.1e · 597dccea
      Matthew Waters authored and Tim-Philipp Müller's avatar Tim-Philipp Müller committed
      openssl 1.1.1e does some stricker EOF handling and will throw an error
      if the EOF is unexpected (like in the middle of a record).  As we are
      streaming data into openssl here, it is entirely possible that we push
      data from multiple buffers/packets into openssl separately.
      
      From the openssl changelog:
      
       Changes between 1.1.1d and 1.1.1e [17 Mar 2020]
        *) Properly detect EOF while reading in libssl. Previously if we hit an EOF
           while reading in libssl then we would report an error back to the
           application (SSL_ERROR_SYSCALL) but errno would be 0. We now add
           an error to the stack (which means we instead return SSL_ERROR_SSL) and
           therefore give a hint as to what went wrong.
           [Matt Caswell]
      
      We can relax the EOF signalling to only return TRUE when we have stopped
      for any reason (EOS, error).
      
      Will also remove a spurious EOF error from previous openssl version.
      
      Part-of: <gstreamer/gst-plugins-bad!1598>
      597dccea
  8. Jun 06, 2020
  9. Feb 14, 2020
  10. Feb 08, 2020
  11. Feb 05, 2020
  12. Jan 20, 2020
    • Seungha Yang's avatar
      msdkdec: Do not use video memory on Windows · 3fbfb790
      Seungha Yang authored and Nirbheek Chauhan's avatar Nirbheek Chauhan committed
      Like msdkenc, do not use video memory by default on Windows.
      3fbfb790
    • Nirbheek Chauhan's avatar
      msdk: Fix increasing memory usage in dynamic pipelines · 2343fd60
      Nirbheek Chauhan authored
      Our context is non-persistent, and we propagate it throughout the
      pipeline. This means that if we try to reuse any gstmsdk element by
      removing it from the pipeline and then re-adding it, we'll clone the
      mfxSession and create a new gstmsdk context as a child of the old one
      inside `gst_msdk_context_new_with_parent()`.
      
      Normally this only allocates a few KB inside the driver, but on
      Windows it seems to allocate tens of MBs which leads to linearly
      increasing memory usage for each PLAYING->NULL->PLAYING state cycle
      for the process. The contexts will only be freed when the pipeline
      itself goes to `NULL`, which would defeat the purpose of dynamic
      pipelines.
      
      Essentially, we need to optimize the case in which the element is
      removed from the pipeline and re-added and the same context is re-set
      on it. To detect that case, we set the context on `old_context`, and
      compare it to the new one when preparing the context. If they're the
      same, we don't need to do anything.
      
      Fixes gstreamer/gst-plugins-bad#946
      2343fd60
    • Nirbheek Chauhan's avatar
      msdk: Reorganize context preparation code · 0a0f929f
      Nirbheek Chauhan authored
      Split it out into a separate function with early exits to make the
      flow clearer, and document what the function is doing clearly.
      No functional changes.
      0a0f929f
    • Nirbheek Chauhan's avatar
  13. Jan 17, 2020
  14. Jan 14, 2020
  15. Jan 13, 2020
Loading