[Bug 679145] gst_buffer_copy and gst_buffer_make_writable semantics

[GStreamer (bugzilla.gnome.org)]

https://bugzilla.gnome.org/show_bug.cgi?id=679145
  GStreamer | gstreamer (core) | git

--- Comment #6 from Mark Nauwelaerts <mnauw at users.sourceforge.net> 2012-07-18 14:08:28 UTC ---
Somewhat related, w.r.t. order of locking EXCLUSIVE / WRITE, also note that
gst_buffer_map_range might well end up with a new piece of memory (from
gst_memory_make_mapped) which is then already mapped (e.g. WRITE) and which
will only then be accepted as buffer memory (and thereby locked EXCLUSIVE).

-- 
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.