[Bug 797152] vaapidec: leak of dmabuf fds when transitioning from PLAYING to NULL state

[GStreamer (GNOME Bugzilla)]

https://bugzilla.gnome.org/show_bug.cgi?id=797152

--- Comment #3 from Víctor Manuel Jáquez Leal <vjaquez at igalia.com> ---
(In reply to Sakari Kapanen from comment #2)
> Would you mind kindly elaborating what is the best
> way to trace the buffers (or how you would do it)? Would it be via GST_DEBUG
> logs or something else?

Yes, using those that are already in the code, or adding more as you need. Also
I would check the leak tracer  tools: 

https://www.collabora.com/news-and-blog/blog/2016/06/20/gstreamer-leaks-tracer/

Check the creation and destruction of buffers on logging fdmemory:5
also the dup of the fd in gstreamer-vaapi gst/vaapi/gstvaapivideomemory.c



> Also, it would be helpful to have some pointers to where dmabuf
> allocation/deallocation takes place in the VAAPI decode elements. I am
> pretty new to the gstreamer-vaapi module and some starting point would be
> very helpful in the investigation.

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
You are the assignee for the bug.