[Bug 796692] sample/bufferlist/buffer: Non-writable container miniobjects allow writable access to their contents, causing memory problems

[GStreamer (GNOME Bugzilla)]

https://bugzilla.gnome.org/show_bug.cgi?id=796692

Sebastian Dröge (slomo) <slomo at coaxion.net> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
            Summary|bufferlist:                 |sample/bufferlist/buffer:
                   |gst_buffer_list_get() can   |Non-writable container
                   |give a writable reference   |miniobjects allow writable
                   |to multiple threads at the  |access to their contents,
                   |same time                   |causing memory problems

--- Comment #23 from Sebastian Dröge (slomo) <slomo at coaxion.net> ---
Ok I'm not really sure how to best implement tracking of the parents of a
miniobject. There is simply no sane way to store anything new in miniobjects
due to a) miniobjects being allocated by the subclass (so we can't overallocate
in gstminiobject.c), b) no padding in GstMiniObject, c) qdata allowing storing
of additional data but it involves more allocations and a *global* mutex.

If someone has any ideas that do not involve going from libgstreamer-1.0.so.0
to .so.1 that would be great :) This is really a serious problem

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
You are the assignee for the bug.