[Bug 727109] New: buffer: Should not set TAG_MEMORY if memory has not been replaced

[GStreamer (bugzilla.gnome.org)]

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

           Summary: buffer: Should not set TAG_MEMORY if memory has not
                    been replaced
    Classification: Platform
           Product: GStreamer
           Version: git
        OS/Version: Linux
            Status: UNCONFIRMED
          Severity: normal
          Priority: Normal
         Component: gstreamer (core)
        AssignedTo: gstreamer-bugs at lists.freedesktop.org
        ReportedBy: nicolas.dufresne at collabora.co.uk
         QAContact: gstreamer-bugs at lists.freedesktop.org
     GNOME version: ---


I'm not completely certain for this one, it needs review. But we recently
introduce the TAG_MEMORY to track if a buffer is suited to got back into the
pool or not. In all places, the tag is only set if memory has been merged or
replaced. The exception is for resize, where we set the flags as soon as 1
buffer is affected by the resize. I think it's an error, it should only set the
flag as soon as one memory get replaced. This is to cover a normal case where
the pool is used for encoded data, where each buffer will have a different used
size.

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