[gstreamer-bugs] [Bug 501546] New: Buffer usage issue in gstreamer plugins for OpenMAX

[GStreamer (bugzilla.gnome.org)]

If you have any questions why you received this email, please see the text at
the end of this email. Replies to this email are NOT read, please see the text
at the end of this email. You can add comments to this bug at:
  http://bugzilla.gnome.org/show_bug.cgi?id=501546

  GStreamer | gst-openmax | Ver: HEAD CVS
           Summary: Buffer usage issue in gstreamer plugins for OpenMAX
           Product: GStreamer
           Version: HEAD CVS
          Platform: Other
        OS/Version: Linux
            Status: UNCONFIRMED
          Severity: normal
          Priority: Normal
         Component: gst-openmax
        AssignedTo: gstreamer-bugs at lists.sourceforge.net
        ReportedBy: diego.melpignano at st.com
         QAContact: gstreamer-bugs at lists.sourceforge.net
     GNOME version: Unspecified
   GNOME milestone: Unspecified


Using the 0.10.0.2 of gst-omx there is a problem with the buffer allocation.
In OpenMAX all the buffers are allocated during the setup with either an
OMX_UseBuffer or an OMX_AllocateBuffer call. These calls also create a buffer
header, which is a structure whose pBuffer member points to the actual memory
buffer. This member is read-only and should not be modified.
During the processing inside gst-openmax plugins pBuffer is overwritten (see
gstomx_base_filter.c line 500 of the latest release 0.10.0.2). 
These buffers have different addresses and size compared to what has been
declared with OMX_UseBuffer(). This behavior is against the OpenMAX spec, and
can cause errors.
In any case the OpenMAX components should check for the correctness of the
buffers received. Also the IL client is not allowed to overwrite the pBuffer
pointer.


-- 
See http://bugzilla.gnome.org/page.cgi?id=email.html for more info about why you received
this email, why you can't respond via email, how to stop receiving
emails (or reduce the number you receive), and how to contact someone
if you are having problems with the system.

You can add comments to this bug at http://bugzilla.gnome.org/show_bug.cgi?id=501546.