[3.0] Stop calling destroy methods of texture and FrameBuffers on RenderManager destr... 32/119132/3
authorFerran Sole <ferran.sole@samsung.com>
Tue, 6 Dec 2016 09:33:51 +0000 (09:33 +0000)
committerNick Holland <nick.holland@partner.samsung.com>
Wed, 15 Mar 2017 15:41:39 +0000 (15:41 +0000)
commitb36f145a5025548a9dba7d77c7d67ece4ff1d80a
tree8e7bf001e9270414fb4141d76bc2d0c9552e2899
parentf02762bc3a7f75d02d2b33b29663b693e56474a9
[3.0] Stop calling destroy methods of texture and FrameBuffers on RenderManager destructor

Crashes because most OpenGL calls get the OpenGL context from
thread local storage. In this case, we're trying to delete
textures on the main thread which has no OpenGL context.

Cherry picked from devel/master branch
https://review.tizen.org/gerrit/#/c/102672/5

Removed destruction of texture and framebuffer resources since they
will be cleaned up automatically when the GL context is destroyed

Change-Id: I67e817a1f40c12b4c6730deb72eb742288575bf1
automated-tests/src/dali/utc-Dali-FrameBuffer.cpp
automated-tests/src/dali/utc-Dali-Texture.cpp
dali/internal/render/common/render-manager.cpp
dali/internal/render/renderers/render-frame-buffer.cpp
dali/internal/render/renderers/render-frame-buffer.h
dali/internal/render/renderers/render-texture.cpp
dali/internal/render/renderers/render-texture.h