From e64fa3eab63110c9ac3864e6cf7ff3a94bed51d6 Mon Sep 17 00:00:00 2001 From: "aa@chromium.org" Date: Fri, 8 Apr 2011 05:18:22 +0000 Subject: Remove unneeded v8 lockers from idb_bindings.cc. Since this code is pulled into webkit_unit_tests, it is making us need lockers there too, which stinks. I don't see any reason for these to exist. My speculation is that this code used to run in the browser process and was needed at that time. BUG= TEST= Review URL: http://codereview.chromium.org/6812038 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@80895 0039d316-1c4b-4281-b951-d872f2087c98 --- webkit/glue/idb_bindings.cc | 3 --- 1 file changed, 3 deletions(-) (limited to 'webkit/glue') diff --git a/webkit/glue/idb_bindings.cc b/webkit/glue/idb_bindings.cc index ae5b508..3149c52 100644 --- a/webkit/glue/idb_bindings.cc +++ b/webkit/glue/idb_bindings.cc @@ -12,7 +12,6 @@ #include "third_party/WebKit/Source/WebKit/chromium/public/WebIDBKeyPath.h" #include "third_party/WebKit/Source/WebKit/chromium/public/WebSerializedScriptValue.h" #include "third_party/WebKit/Source/WebKit/chromium/public/WebString.h" -#include "v8/include/v8.h" namespace webkit_glue { @@ -24,7 +23,6 @@ bool IDBKeysFromValuesAndKeyPath( const std::vector& serialized_script_values, const string16& idb_key_path, std::vector* values) { - v8::Locker lock; WebIDBKeyPath web_idb_key_path = WebIDBKeyPath::create(idb_key_path); bool error = web_idb_key_path.parseError() != 0; // TODO(bulach): what to do when we have a parse error? For now, setting @@ -46,7 +44,6 @@ WebSerializedScriptValue InjectIDBKey( const WebIDBKey& key, const WebSerializedScriptValue& value, const string16& idb_key_path) { - v8::Locker lock; return WebIDBKey::injectIDBKeyIntoSerializedValue( key, value, WebIDBKeyPath::create(idb_key_path)); } -- cgit v1.1