[EvasGL] Fix to 3D memory leak.
authorWonsik, Jung <sidein@samsung.com>
Thu, 17 Nov 2016 13:29:31 +0000 (22:29 +0900)
committerJinYong Park <j4939.park@samsung.com>
Tue, 22 Nov 2016 10:36:40 +0000 (19:36 +0900)
commit052f6b19bab7dbe550af3879f7c2e7057d4501e8
tree7fed005453ca992814d66111035c76a468e1827d
parent3d50b7307e0d99b846fa87d10bf481d05f2162fe
[EvasGL] Fix to 3D memory leak.

If evas_gl_make_current is called with NULL,
and evgl_surface_destroy and evgl_context_destroy is called,
3D memory leak occurs.
Because rsc->current_ctx is NULL in evas_gl_make_current
and texture and framebuffer can not be free in destroy funnctions.
To fix that, one value is added to EVGL_resource.
This value is kept with current_ctx, when evas_gl_make_current is called with NULL.

Change-Id: Iabb7685d0c5e932b0e08e716225bf15f58696d0b
src/modules/evas/engines/gl_common/evas_gl_core.c
src/modules/evas/engines/gl_common/evas_gl_core_private.h