[Bug 744303] bufferpool: Don't free GstBuffer if memory isn't writable

GStreamer (GNOME Bugzilla) bugzilla at gnome.org
Sun Feb 15 19:11:24 PST 2015


Olivier CrĂȘte <olivier.crete at ocrete.ca> changed:

           What    |Removed                     |Added
                 CC|                            |olivier.crete at ocrete.ca

--- Comment #2 from Olivier CrĂȘte <olivier.crete at ocrete.ca> ---
@nicolas: This is how sub-buffering worked in 0.10. I guess Wim had a good
reason to remove it. 

I understand the current design is that the GstBuffer object just isn't
poolable in that case, making the buffer pools pretty much useless for a lot of
cases. That said, the GstMemory is just a small structure coming out of the
slice allocator, so it shouldn't matter much. And frankly, I'd like to see some
number about the usefulness of the pooling behavior of GstBufferPool in 1.x.

Parenting one buffer to another means that even if only one GstMemory of a
GstBuffer is still in use, then all GstMemories in it would be stuck.

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