Fix stale reinit in the shader translator.
commit31baa98a81704819c52f04111f802973d81eba17
authorbajones@chromium.org <bajones@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98>
Tue, 25 Feb 2014 18:21:12 +0000 (25 18:21 +0000)
committerbajones@chromium.org <bajones@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98>
Tue, 25 Feb 2014 18:21:12 +0000 (25 18:21 +0000)
tree176c4117148fe9b8826bc26d38a231f0515ca443
parent4f8fd780d9f89de79b4db6bdb2b555a4fabcc255
Fix stale reinit in the shader translator.

In some cases we would initialize, free, then re-initialize the
shader translator within the same initialized memory. The local
static tracking initialization would get stuck and we would fail
on subsequent calls. We can fix this by using a non-local static.

We ran into this problem in some unit tests which use the
in-process GPU, likely because of the single-process model.

BUG=344043
R=zmo@chromium.org, jbauman@chromium.org

Review URL: https://codereview.chromium.org/178043002

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@253205 0039d316-1c4b-4281-b951-d872f2087c98
DEPS
gpu/command_buffer/service/shader_translator.cc