From 6bb560a4ebb52a48003872512a7c45afa3153639 Mon Sep 17 00:00:00 2001
From: Julien Isorce <j.isorce@samsung.com>
Date: Wed, 28 Oct 2015 14:41:54 +0000
Subject: [PATCH] glslstage: initialize output params to 0 before calling gl
 functions

The client side API of the Chromium's GPU Process has asserts
in debug mode that check that output params are initialized to 0.
---
 gst-libs/gst/gl/gstglslstage.c | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/gst-libs/gst/gl/gstglslstage.c b/gst-libs/gst/gl/gstglslstage.c
index 4cd518ae64..062b29ae50 100644
--- a/gst-libs/gst/gl/gstglslstage.c
+++ b/gst-libs/gst/gl/gstglslstage.c
@@ -471,8 +471,10 @@ _compile_shader (GstGLContext * context, struct compile *data)
   gl->CompileShader (priv->handle);
   /* FIXME: supported threaded GLSL compilers and don't destroy compilation
    * performance by getting the compilation result directly after compilation */
+  status = GL_FALSE;
   gl->GetShaderiv (priv->handle, GL_COMPILE_STATUS, &status);
 
+  len = 0;
   vtable->GetShaderInfoLog (priv->handle, sizeof (info_buffer) - 1, &len,
       info_buffer);
   info_buffer[len] = '\0';