[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 #2 from Sakari Kapanen <sakari.m.kapanen at gmail.com> ---
(In reply to Víctor Manuel Jáquez Leal from comment #1)

Thank you for the quick response.

> (In reply to Sakari Kapanen from comment #0)
> > Even though the attached code uses a home-baked function that counts the
> > open dmabuf fds, the behaviour can be verified by e.g. watching the output
> > of lsof:
> > lsof -p $(pidof repro) | grep -c dmabuf
> > 
> > I would appreciate any input on how to resolve the issue (or if you can
> > confirm it's an actual bug in gstreamer-vaapi or some other element).
> 
> Tracing the created buffers and detect those which aren't deallocated and
> deallocate them at the right moment.

Sounds sensible to me. 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?

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.