WGC3DCommandBufferImpl: Acquire lock when accessing share group.

Grab the share group lock when accessing the list and also to assure that ShareGroup creation is not racy.

Also do not use an existing ShareGroup is we are not sharing resources.

Remove the nowadays unused share_resources flag that was still being passed around.

On a related note, remove the non-threadsafe
SetGLES2ImplementationForDestruction() which is fortunately unused.
(It was used by StrictSharedIdHandler once, but the current handlers
don't need to talk to the commandbuffer during destruction.)

TBR=brettw@chromium.org
NOTRY=True

Review URL: https://chromiumcodereview.appspot.com/20826002

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@214242 0039d316-1c4b-4281-b951-d872f2087c98

1 files changed, 0 insertions, 2 deletions

diff --git a/gpu/command_buffer/tests/gl_manager.cc b/gpu/command_buffer/tests/gl_manager.cc
index f4f6c36..c4b84a2 100644
--- a/gpu/command_buffer/tests/gl_manager.cc
+++ b/gpu/command_buffer/tests/gl_manager.cc
@@ -70,7 +70,6 @@ void GLManager::Initialize(const GLManager::Options& options) {
   const size_t kStartTransferBufferSize = 4 * 1024 * 1024;
   const size_t kMinTransferBufferSize = 1 * 256 * 1024;
   const size_t kMaxTransferBufferSize = 16 * 1024 * 1024;
-  const bool kShareResources = true;
 
   context_lost_allowed_ = options.context_lost_allowed;
 
@@ -200,7 +199,6 @@ void GLManager::Initialize(const GLManager::Options& options) {
       gles2_helper_.get(),
       client_share_group,
       transfer_buffer_.get(),
-      kShareResources,
       options.bind_generates_resource,
       options.image_factory));