[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 #5 from Mark Nauwelaerts <mnauw at users.sourceforge.net> 2012-07-18 13:37:38 UTC ---
Created an attachment (id=219124)
 View: https://bugzilla.gnome.org/attachment.cgi?id=219124
 Review: https://bugzilla.gnome.org/review?bug=679145&attachment=219124

tests: gstbuffer: extend buffer copy test

Looks like we may still be having some problems in coming up with really
independent buffer copies, so re-opening this.

Reading code suggests this can indeed happen in the sequence:
* locking EXCLUSIVE some fresh memory
* mapping it WRITE
* then making a buffer copy, adding another EXCLUSIVE lock
* mapping it WRITE again

Attached patch extends the unit test to illustrate/test this.

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