Fix an assertion beneath SerializedScriptValue::deserialize on 32-bit builds (e.g., on Windows)
Passing a JSValue to toRef on 32-bit builds can perform an allocation, so we need to make sure we hold a JSLock when that occurs. Reviewed by Oliver Hunt. * bindings/js/SerializedScriptValue.cpp: (WebCore::SerializedScriptValueData::serialize): (WebCore::SerializedScriptValueData::deserialize): Moved JSLocks from here... (WebCore::SerializedScriptValue::create): (WebCore::SerializedScriptValue::deserialize): ...to this higher level, from which toRef can be called. git-svn-id: svn://svn.chromium.org/blink/trunk@54023 bbb929c8-8fbe-4397-9dbb-9b2b20218538
Showing
Please register or sign in to comment