summaryrefslogtreecommitdiffstats
path: root/base/string_util.h
diff options
context:
space:
mode:
authorjbates@chromium.org <jbates@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98>2011-07-07 20:44:33 +0000
committerjbates@chromium.org <jbates@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98>2011-07-07 20:44:33 +0000
commit16adff66ea7224ddd91d01160a7bcc54f5d8b5a6 (patch)
tree89f6964ede070dc3809db976e6528f0f11d993a1 /base/string_util.h
parentf3d5a44568be26375eac9daa7c1a69e36ea6f1bf (diff)
downloadchromium_src-16adff66ea7224ddd91d01160a7bcc54f5d8b5a6.zip
chromium_src-16adff66ea7224ddd91d01160a7bcc54f5d8b5a6.tar.gz
chromium_src-16adff66ea7224ddd91d01160a7bcc54f5d8b5a6.tar.bz2
We were synchronously destroying the RendererGlContext transfer buffers while commands may still be pending in the command buffer that use them. This generated spurious kOutOfBounds errors. kOutOfBounds errors cause us to kill the associated GpuChannel. That leads to lots of bad behavior, such as failing to reload certain WebGL demos.
This change simply lets the command buffer destroy the shared memory in its destructor instead of destroying them explicitly. The GPU-side resources are cleaned up when the command buffer is destroyed. BUG=88115 TEST=Open NVIDIA Command Buffer Object WebGL demo; Refresh; Verify successful refresh. Review URL: http://codereview.chromium.org/7301010 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@91747 0039d316-1c4b-4281-b951-d872f2087c98
Diffstat (limited to 'base/string_util.h')
0 files changed, 0 insertions, 0 deletions