Branch: refs/heads/main
Home: https://github.com/WebKit/WebKit
Commit: 653b77d5bdddf7d4ee348ab54a51afd582884b85
https://github.com/WebKit/WebKit/commit/653b77d5bdddf7d4ee348ab54a51afd582884b85
Author: Mitesh Gulecha <[email protected]>
Date: 2026-09-24 (Thu, 24 Sep 2026)
Changed paths:
M Source/JavaScriptCore/runtime/ArrayBuffer.cpp
M Source/JavaScriptCore/runtime/BufferMemoryHandle.cpp
M Source/JavaScriptCore/runtime/Options.cpp
M Source/JavaScriptCore/wasm/WasmMemory.cpp
M Source/WTF/wtf/win/OSAllocatorWin.cpp
Log Message:
-----------
Re-enable wasm fast memory on Windows and stop committing the guard region
https://bugs.webkit.org/show_bug.cgi?id=304154
Reviewed by Ian Grunert.
We were committing the 4 GiB guard/redzone with
PAGE_NOACCESS on Windows, exhausting commit space
and forcing wasm fast memory off.
This change ensures guard ranges actually fault
without consuming commit space, fixing the prior
behavior where a guard request could leave an
accessible range untouched. In
OSAllocator::tryProtect's guard branch, we now
inspect the page state and enforce no-access:
reserve if free, noop if already reserved, and
VirtualProtect to PAGE_NOACCESS if committed.
* Source/WTF/wtf/win/OSAllocatorWin.cpp:
(WTF::OSAllocator::tryProtect):
Canonical link: https://commits.webkit.org/321850@main
To unsubscribe from these emails, change your notification settings at
https://github.com/WebKit/WebKit/settings/notifications
