GNOME Bugzilla – Bug 681152
[0.11] gst_buffer_make_writable also tries to make memory writable
Last modified: 2012-08-03 16:49:42 UTC
In my pipeline, some element tries to call gst_buffer_make_writable on a _readonly_ framebuffer allocated by an upstream hardware element, just to change a buffer flag. Unfortunately the gst_buffer_make_writable also makes its memory writable, and in this case triggers a full copy of the frame buffer. This is obviously overkill just to change a buffer flag. Is there any way this could be avoided, besides not marking the memory read only ?
Sorry I had set the NO_SHARE flag on the memory, the problem was not the READONLY flag. This is working as expected, closing the bug