1. 28 Feb, 2019 7 commits
  2. 27 Feb, 2019 8 commits
  3. 26 Feb, 2019 3 commits
  4. 24 Feb, 2019 4 commits
  5. 21 Feb, 2019 2 commits
  6. 20 Feb, 2019 1 commit
  7. 19 Feb, 2019 15 commits
    • Tim-Philipp Müller's avatar
    • Tim-Philipp Müller's avatar
    • Tim-Philipp Müller's avatar
    • Tim-Philipp Müller's avatar
    • Tim-Philipp Müller's avatar
    • Tim-Philipp Müller's avatar
    • Tim-Philipp Müller's avatar
    • Alex Ashley's avatar
      curlhttpsrc: set BUFFER_OFFSET when creating GstBuffer · dbe0a8cb
      Alex Ashley authored
      To make curlhttpsrc behave more like souphttpsrc, set the
      BUFFER_OFFSET in its output buffers to match the segment
      start. This means that in a HTTP RANGE request, the BUFFER_OFFSET
      will match the value in the RANGE request.
    • Alex Ashley's avatar
      curlhttpsrc: export same HTTP error status as souphttpsrc · 2d806477
      Alex Ashley authored
      To make it closer to a drop-in replacement for souphttpsrc,
      expose the same gst_error_message_with_details as souphttpsrc,
      so that applications can received the HTTP status code and reason
      when an error occurs.
    • Alex Ashley's avatar
      curlhttpsrc: fix various leaks and thread safety issues · c2fe4e58
      Alex Ashley authored
      curlhttpsrc uses a single thread running the
      gst_curl_http_src_curl_multi_loop() function to handle receiving
      data and messages from libcurl. Each instance of curlhttpsrc adds
      an entry into a queue in GstCurlHttpSrcMultiTaskContext and waits
      for the multi_loop to perform the HTTP request.
      Valgrind has shown up race conditions and memory leaks:
      1. gst_curl_http_src_change_state() does not wait for the multi_loop
         to complete before going to the NULL state, which means that
         an instance of GstCurlHttpSrc can be released while
         gst_curl_http_src_curl_multi_loop() still has a reference to it.
      2. if multiple elements try to be removed from the queue at once,
         only the last one is deleted.
      3. source->caps is leaked
      4. curl multi_handle is leaked
      5. leak of curl_handle if URI not set
      6. leak of http_headers when reusing element
      7. null pointer dereference in negotiate caps
      8. double-free of the default user-agent string
      9. leak of multi_task_context.task
      This commit changes the logic so that each element has a connection
      status, which is used by the multi_loop to decide when to remove an
      element from its queue. An instance of curlhttpsrc will not enter
      the NULL state until its reference has been removed from the queue.
      When shutting down the curl multi loop, the memory allocated from the
      call to curl_multi_init() is now released.
      When gstadaptivedemux uses a URI source element, it will re-use
      it for multiple requests, moving it between READY and PLAYING
      between each request. curlhttpsrc was leaking the http_headers
      structure in this use case.
      The gst_curl_http_src_negotiate_caps() function extracts the
      "response-headers" field from the http_headers, but did not check
      that this field might be NULL.
      If the user-agent property is set, the global user-agent string
      was freed. This caused a double-free error if the user-agent is
      ever set a second time during the execution of the process.
      There are situations within curlhttpsrc where the code needs
      both the global multi_task_context mutex and the per-element
      buffer_mutex. To avoid deadlocks, it is vital that the order in
      which these are requested is always the same. This commit modifies
      the locking order to always be in the order:
       1. multi_task_context.task_rec_mutex
       2. buffer_mutex
      Fixes #876
    • Alex Ashley's avatar
      tests: curlhttpsrc: add unit tests · d2d912f3
      Alex Ashley authored
      Based upon the souphttpsrc tests, add unit tests for the curlhttpsrc
      element. The souphttpsrc tests are able to use an HTTP server that
      is provided as part of the soup library. This does not exist in the
      curl library, therefore these tests provide a very simple HTTP server
      using the GIO library.
      These curlhttpsrc tests contain one new test that does not come from
      the souphttpsrc tests. The test_multiple_http_requests test tries to
      reproduce the way in which GstAdaptiveDemux makes use of URI source
      elements. GstAdaptiveDemux creates a bin with the httpsrc element
      and a queue element and sets the locked state of that bin to TRUE,
      so that it does not follow the state transitions of its parent. It
      then moves this bin to the PLAYING state to start each download and
      back to READY when the download completes.
    • Haihao Xiang's avatar
      msdkvpp: allow UYVY in DMABuf mode in the sink pad · 8213d0b8
      Haihao Xiang authored
      Tested with the pipeline below:
      gst-launch-1.0 videotestsrc num-buffers=1 ! msdkvpp ! \
      video/x-raw\(memory:DMABuf\),format=UYVY ! msdkvpp ! video/x-raw, \
      format=YUY2 ! filesink location=a.yuv
    • Haihao Xiang's avatar
      msdkvpp: allow UYVY in the src pad · 56cada69
      Haihao Xiang authored
      This make the pipeline below works:
      gst-launch-1.0 videotestsrc num-buffers=1 ! msdkvpp ! \
      video/x-raw,format=UYVY ! filesink location=a.yuv
      Once https://github.com/intel/media-driver/pull/526 in the media-driver
      is merged, the pipeline below also works:
      gst-launch-1.0 videotestsrc num-buffers=1 ! msdkvpp ! \
      video/x-raw\(memory:DMABuf\),format=UYVY ! filesink location=a.yuv
    • Haihao Xiang's avatar
    • Haihao Xiang's avatar
      msdkvpp: allow BGRx in DMABuf mode in the src pad · ea6789fe
      Haihao Xiang authored
      Tested with the pipeline below:
      gst-launch-1.0 videotestsrc ! msdkvpp ! \
      video/x-raw\(memory:DMABuf\),format=BGRx ! glimagesink