After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 681152 - [0.11] gst_buffer_make_writable also tries to make memory writable
[0.11] gst_buffer_make_writable also tries to make memory writable
Status: RESOLVED NOTABUG
Product: GStreamer
Classification: Platform
Component: gstreamer (core)
git master
Other Linux
: Normal normal
: git master
Assigned To: GStreamer Maintainers
GStreamer Maintainers
Depends on:
Blocks:
 
 
Reported: 2012-08-03 16:40 UTC by Arnaud Vrac
Modified: 2012-08-03 16:49 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Arnaud Vrac 2012-08-03 16:40:31 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 ?
Comment 1 Arnaud Vrac 2012-08-03 16:49:42 UTC 
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