Branch: refs/heads/webkitglib/2.52
Home: https://github.com/WebKit/WebKit
Commit: 235b222f37a97a7e8136f7bc31961f6149b0592d
https://github.com/WebKit/WebKit/commit/235b222f37a97a7e8136f7bc31961f6149b0592d
Author: Lauro Moura <[email protected]>
Date: 2026-07-06 (Mon, 06 Jul 2026)
Changed paths:
M Source/WebCore/platform/network/soup/NetworkStorageSessionSoup.cpp
Log Message:
-----------
Cherry-pick 316492@main (86ec57b01ddf).
https://bugs.webkit.org/show_bug.cgi?id=318463
[Soup] Null deref in
NetworkStorageSession::stopListeningForCookieChangeNotifications when a host is
absent from m_cookieChangeObservers
https://bugs.webkit.org/show_bug.cgi?id=318463
Reviewed by Patrick Griffis.
Safely ignore a given host if it's not found in m_cookieChangeObservers,
avoiding a potential null deref. This mirrors the Cocoa port's release
behavior. For debug builds, as the ASSERT_UNUSED(removed, removed) in
NetworkConnectionToWebProcess::unsubscribeFromCookieChangeNotifications
would have triggered earlier, we're also removing the redundant ASSERT.
This scenario can happen after a previous NetworkProcess with cookie
listeners crashes. As currently the WebCookieJar is not notified of such
crashes, it does not tell the replacement process's NetworkStorageSession
about the existing listeners. Then, when the WebCookieJar sends an
unsubscribe request, we hit the assertion or trigger the null deref on
the empty map on the storage session.
* Source/WebCore/platform/network/soup/NetworkStorageSessionSoup.cpp:
(WebCore::NetworkStorageSession::stopListeningForCookieChangeNotifications):
Canonical link: https://commits.webkit.org/316492@main
Canonical link: https://commits.webkit.org/305877.960@webkitglib/2.52
Commit: c9710b82a657c7f334320ea01fb0fe450846844f
https://github.com/WebKit/WebKit/commit/c9710b82a657c7f334320ea01fb0fe450846844f
Author: Justin Michaud <[email protected]>
Date: 2026-07-06 (Mon, 06 Jul 2026)
Changed paths:
M Tools/Scripts/run-jsc-stress-tests
Log Message:
-----------
Cherry-pick 316479@main (7d6af3d9a4c3).
https://bugs.webkit.org/show_bug.cgi?id=318505
Update arch detection in run-jsc-stress-tests
https://bugs.webkit.org/show_bug.cgi?id=318505
Reviewed by Yusuke Suzuki.
arm64 and riscv64 have arch identifiers that don't look like ascii.
Let's compare them as bytes instead to avoid string encoding headaches.
Canonical link: https://commits.webkit.org/316479@main
Canonical link: https://commits.webkit.org/305877.961@webkitglib/2.52
Compare: https://github.com/WebKit/WebKit/compare/b10717a4d877...c9710b82a657
To unsubscribe from these emails, change your notification settings at
https://github.com/WebKit/WebKit/settings/notifications
