[Bug 758039] gstgl: fix memory leaks and memory mishandlings
GStreamer (GNOME Bugzilla)
bugzilla at gnome.org
Thu Nov 12 22:07:53 PST 2015
https://bugzilla.gnome.org/show_bug.cgi?id=758039
Matthew Waters <ystreet00 at gmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
CC| |ystreet00 at gmail.com
Resolution|--- |FIXED
--- Comment #6 from Matthew Waters <ystreet00 at gmail.com> ---
commit 6eae0c7e189f69c71cc3b0cf00e4fcdec172a13e
Author: Vineeth TM <vineeth.tm at samsung.com>
Date: Fri Nov 13 10:41:58 2015 +0900
glsl: fix possible string overrun in gst_glsl_version_profile_from_string
given a NULL-terminated string, s.
s[i] = '\0';
i++;
does not guarentee that s[i] is NULL terminated and thus string operations
could read off the end of the array.
https://bugzilla.gnome.org/show_bug.cgi?id=758039
commit babd066b894fc3694693a2abb3cd0d8c6a66992e
Author: Matthew Waters <matthew at centricular.com>
Date: Fri Nov 13 16:50:22 2015 +1100
glshader: don't read invalid list pointers (use after free)
gst_gl_shader_detach_unlocked already removes the list entry so attempting
to
use the element to iterate to the next stage could read invalid data.
Based on patch by Vineeth TM <vineeth.tm at samsung.com>
https://bugzilla.gnome.org/show_bug.cgi?id=758039
commit e940d8875d01210ecc6ac280d5a91a6856bcb8f2
Author: Vineeth TM <vineeth.tm at samsung.com>
Date: Fri Nov 13 10:44:26 2015 +0900
tests:glsl: version_profile_s string leak
https://bugzilla.gnome.org/show_bug.cgi?id=758039
commit 4c9ac5e474e22a48e476f4b9983e21260798883f
Author: Vineeth TM <vineeth.tm at samsung.com>
Date: Fri Nov 13 10:56:10 2015 +0900
glsl: free str while returning error
https://bugzilla.gnome.org/show_bug.cgi?id=758039
commit a22f085eac42c2aeced4800e1c3332b508e642a8
Author: Vineeth TM <vineeth.tm at samsung.com>
Date: Fri Nov 13 11:04:34 2015 +0900
tests:glupload: fix caps memory leak
https://bugzilla.gnome.org/show_bug.cgi?id=758039
--
You are receiving this mail because:
You are the QA Contact for the bug.
You are the assignee for the bug.
More information about the gstreamer-bugs
mailing list