[Bug 783776] New: gsteglimage: eglDestroyImage is used for images created by eglCreateImageKHR

[GStreamer (GNOME Bugzilla)]

https://bugzilla.gnome.org/show_bug.cgi?id=783776

            Bug ID: 783776
           Summary: gsteglimage: eglDestroyImage is used for images
                    created by eglCreateImageKHR
    Classification: Platform
           Product: GStreamer
           Version: 1.12.0
                OS: Linux
            Status: NEW
          Severity: critical
          Priority: Normal
         Component: gst-plugins-bad
          Assignee: gstreamer-bugs at lists.freedesktop.org
          Reporter: HHG01200 at nifty.ne.jp
        QA Contact: gstreamer-bugs at lists.freedesktop.org
     GNOME version: ---

On RaspberryPi3 (RASPBIAN JESSIE), without EGL_VERSION_1_5 macro,
_gst_egl_image_create() uses eglCreateImageKHR() .
But _gst_egl_image_destroy() uses eglDestroyImage() if it is available.
Broadcom VideoCore library EGL provide valid function address of
eglDestroyImage(), but it is not same as eglDestroyImageKHR().
eglDestroyImage() always fails and a debug message "eglDestroyImage failed" is
output.
Thus memory leak.
If eglDestroyImageKHR() is used, it succeeds.

How to reproduce:
> export GST_DEBUG=2
> gst-launch-1.0 filesrc location=<videofile> ! decodebin ! glimagesink
   :
   :
0:01:53.499545048  2300  0x1a27520 WARN              gleglimage
gsteglimage.c:295:_gst_egl_image_destroy:<glcontextegl0> eglDestroyImage failed
0:01:53.506686259  2300  0x1a27520 WARN              gleglimage
gsteglimage.c:295:_gst_egl_image_destroy:<glcontextegl0> eglDestroyImage failed
0:01:53.507043497  2300  0x1a27520 WARN              gleglimage
gsteglimage.c:295:_gst_egl_image_destroy:<glcontextegl0> eglDestroyImage failed
0:01:53.507303860  2300  0x1a27520 WARN              gleglimage
gsteglimage.c:295:_gst_egl_image_destroy:<glcontextegl0> eglDestroyImage failed
0:01:53.507561046  2300  0x1a27520 WARN              gleglimage
gsteglimage.c:295:_gst_egl_image_destroy:<glcontextegl0> eglDestroyImage failed
Setting pipeline to NULL ...
Freeing pipeline ...

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
You are the assignee for the bug.