Branch: refs/heads/main
Home: https://github.com/WebKit/WebKit
Commit: 176b030fd3da958bd73586897a62e45e70f46c70
https://github.com/WebKit/WebKit/commit/176b030fd3da958bd73586897a62e45e70f46c70
Author: Menlodorian <[email protected]>
Date: 2026-01-21 (Wed, 21 Jan 2026)
Changed paths:
M Source/JavaScriptCore/runtime/JSLock.cpp
M Source/JavaScriptCore/runtime/JSLock.h
Log Message:
-----------
Add diagnostics to help debug a crash in JSLock::unlock().
https://bugs.webkit.org/show_bug.cgi?id=305998
rdar://166016998
Reviewed by Yusuke Suzuki.
We're seeing a mysterious RELEASE_ASSERT failure due to the JSLock not being
held by the
current thread when it should be. This patch adds the collection of
diagnostics data
about the state of the JSLock only when it is found to be in this inconsistent
state.
Otherwise, there is no behavior change.
No new tests because this does not change normal behavior. It only adds
diagnostics for
when a crash is imminent.
* Source/JavaScriptCore/runtime/JSLock.cpp:
(JSC::JSLock::didAcquireLock):
(JSC::JSLock::dumpInfoAndCrashForLockNotOwned):
(JSC::JSLock::DropAllLocks::DropAllLocks):
* Source/JavaScriptCore/runtime/JSLock.h:
Canonical link: https://commits.webkit.org/305986@main
To unsubscribe from these emails, change your notification settings at
https://github.com/WebKit/WebKit/settings/notifications
