[Bug 707534] BufferPool don't buffer GstMemory in 1.x

GStreamer (bugzilla.gnome.org) bugzilla at gnome.org
Sat Oct 26 11:41:48 CEST 2013


https://bugzilla.gnome.org/show_bug.cgi?id=707534
  GStreamer | gstreamer (core) | git

--- Comment #4 from Olivier Crete (Tester) <olivier.crete at ocrete.ca> 2013-10-26 09:41:43 UTC ---
Had a long IRC discussion with Wim about this. He doesn't think we need to have
a memory pool at all, he thinks the GstAllocator subclass should do that on
their own, I'll re-write some of my branch to match that. I'll try to split up
the patches at the same time.

The draining stuff is indeed orthogonal.

The reason for gst_allocator_wait_for_empty() is that once we remove the
NO_SHARE flag on on the buffers (which is evil), then the GstMemory could get
attached to buffers created by someone else (for example, if an element
sub-buffers), so the GstBuffers may be back in the pool, but it doesn't mean
all of the memory has been freed.

-- 
Configure bugmail: https://bugzilla.gnome.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
You are the assignee for the bug.


More information about the gstreamer-bugs mailing list