Branch: refs/heads/main
Home: https://github.com/WebKit/WebKit
Commit: 76b34686210f4f6779053590e7b9cfb1eadf6a15
https://github.com/WebKit/WebKit/commit/76b34686210f4f6779053590e7b9cfb1eadf6a15
Author: Yusuke Suzuki <[email protected]>
Date: 2026-05-28 (Thu, 28 May 2026)
Changed paths:
A JSTests/wasm/stress/instance-anchor.js
M Source/JavaScriptCore/wasm/js/JSWebAssemblyInstance.cpp
Log Message:
-----------
[JSC] Wasm::InstanceAnchor should be unregistered at the prologue of
JSWebAssemblyInstance destructor
https://bugs.webkit.org/show_bug.cgi?id=310234
rdar://172821924
Reviewed by Yijia Huang.
Wasm::InstanceAnchor can expose JSWebAssemblyInstance to the other
threads including compiler. Thus if we would like to start destroying
JSWebAssemblyInstance, we should first unregister Wasm::InstanceAnchor
before destroying any part of JSWebAssemblyInstance.
Test: JSTests/wasm/stress/instance-anchor.js
* JSTests/wasm/stress/instance-anchor.js: Added.
(bury):
(main.warmUpInstanceB):
(main):
* Source/JavaScriptCore/wasm/js/JSWebAssemblyInstance.cpp:
(JSC::JSWebAssemblyInstance::~JSWebAssemblyInstance):
Originally-landed-as: 305413.527@rapid/safari-7624.2.5.110-branch
(eecf636daa52). rdar://176062434
Canonical link: https://commits.webkit.org/314101@main
To unsubscribe from these emails, change your notification settings at
https://github.com/WebKit/WebKit/settings/notifications
