GNOME Bugzilla – Bug 712612
v4l2bufferpool: take over the floating reference for the new allocator
Last modified: 2014-01-17 13:56:33 UTC
Created attachment 260144 [details] [review] patch Otherwise the allocator will never be deleted.
Comment on attachment 260144 [details] [review] patch This looks wrong, we should probably just make all GstAllocators non-floating in the instance_init function. And the real bug in the previous code here is that we also ref() the newly created allocator. Everything should work just fine with your patch but without the ref_sink() call here
Is this still needed with all the changes that happened on master ?
Created attachment 266524 [details] [review] patch Same as the last patch but without the ref_sink. Also rebased to latest master. It's still needed.
Review of attachment 266524 [details] [review]: Looks good, I'll merge and push
Review of attachment 266524 [details] [review]: commit 3d2bd4ff4975baac82885a258fa4ac21e90c7660 Author: Michael Olbrich <m.olbrich@pengutronix.de> Date: Fri Jan 17 07:46:09 2014 +0100 v4l2bufferpool: don't ref the newly created allocator Otherwise the allocator will never be deleted. https://bugzilla.gnome.org/show_bug.cgi?id=712612
No need to backport, I don't think dmabuf works there in stable branch, but correct me if I'm wrong.