https://bugs.webkit.org/show_bug.cgi?id=175256
Reviewed by Saam Barati.
The check in createFromBytes just needed to check that the buffer was not null before
calling isCaged.
* runtime/ArrayBuffer.cpp:
(JSC::ArrayBuffer::createFromBytes):
git-svn-id: https://svn.webkit.org/repository/webkit/trunk@220330
268f45cc-cd09-0410-ab3c-
d52691b4dbfc
+2017-08-07 Keith Miller <keith_miller@apple.com>
+
+ REGRESSION: wasm.yaml/wasm/js-api/dont-mmap-zero-byte-memory.js failing on JSC Debug bots
+ https://bugs.webkit.org/show_bug.cgi?id=175256
+
+ Reviewed by Saam Barati.
+
+ The check in createFromBytes just needed to check that the buffer was not null before
+ calling isCaged.
+
+ * runtime/ArrayBuffer.cpp:
+ (JSC::ArrayBuffer::createFromBytes):
+
2017-08-05 Carlos Garcia Campos <cgarcia@igalia.com>
[GTK][WPE] Add API to provide browser information required by automation
// - WebAssembly. Wasm should allocate from the cage.
Ref<ArrayBuffer> ArrayBuffer::createFromBytes(const void* data, unsigned byteLength, ArrayBufferDestructorFunction&& destructor)
{
- if (!Gigacage::isCaged(data) && data && byteLength)
+ if (data && byteLength && !Gigacage::isCaged(data))
Gigacage::disableGigacage();
ArrayBufferContents contents(const_cast<void*>(data), byteLength, WTFMove(destructor));