[Bug 724481] bufferpool: Doesn't reset buffers when releasing them to the pool
GStreamer (bugzilla.gnome.org)
bugzilla at gnome.org
Thu Feb 27 06:26:14 PST 2014
https://bugzilla.gnome.org/show_bug.cgi?id=724481
GStreamer | gstreamer (core) | git
--- Comment #12 from Wim Taymans <wim.taymans at gmail.com> 2014-02-27 14:47:49 UTC ---
commit f22d8f08e0a52c6f23520d67fba6b7e1aae61e6e
Author: Wim Taymans <wtaymans at redhat.com>
Date: Thu Feb 27 15:14:59 2014 +0100
bufferpool: Use TAG_MEMORY to check memory before releasing
Tag allocated buffers with TAG_MEMORY. When they are released later,
only add them back to the pool if the tag is still there and the memory
has not been changed, otherwise throw the buffer away.
Add unit test to check various scenarios.
Fixes https://bugzilla.gnome.org/show_bug.cgi?id=724481
commit 5bca002f4bcb37e3c5453c77a750bb741e3cfea1
Author: Wim Taymans <wtaymans at redhat.com>
Date: Thu Feb 27 14:35:09 2014 +0100
buffer: add a new flag to track memory changes
Add a flag to check if the memory changed in a buffer.
--
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