Branch: refs/heads/webkitglib/2.44
Home: https://github.com/WebKit/WebKit
Commit: 69c582be05a46699bda0bd400f33e4782c0ac1c8
https://github.com/WebKit/WebKit/commit/69c582be05a46699bda0bd400f33e4782c0ac1c8
Author: Ben Nham <[email protected]>
Date: 2024-04-26 (Fri, 26 Apr 2024)
Changed paths:
M Source/WTF/wtf/MemoryPressureHandler.cpp
M Source/WTF/wtf/MemoryPressureHandler.h
M Source/WTF/wtf/cocoa/MemoryPressureHandlerCocoa.mm
M Source/WTF/wtf/unix/MemoryPressureHandlerUnix.cpp
M Source/WTF/wtf/win/MemoryPressureHandlerWin.cpp
M Source/WebKit/WebProcess/WebProcess.cpp
Log Message:
-----------
Cherry-pick 275198@main (a45b3b20b106).
https://bugs.webkit.org/show_bug.cgi?id=269859
WebContent process stays in the isUnderMemoryPressure state forever after
it breaches the PROC_LIMIT_CRITICAL threshold
https://bugs.webkit.org/show_bug.cgi?id=269859
rdar://118126701
Reviewed by Antti Koivisto.
After 244148@main, a WebContent process that exceeds the
PROC_LIMIT_CRITICAL threshold ends up in
the isUnderMemoryPressure state forever. This is because we were mutating
the memory pressure state
instance variable when handling the process limit notification. Since the
OS only notifies you when
you exceed the proc limit, but not when you go back under the proc limit,
that state variable ended
up staying in the critical state forever. (This bug has occurred before,
see r234646.)
To fix this, stop mutating the memory pressure state when the process limit
notification fires, and
add a separate callback for handling process limit notifications.
* Source/WTF/wtf/MemoryPressureHandler.cpp:
(WTF::MemoryPressureHandler::setMemoryPressureStatus):
(WTF::MemoryPressureHandler::memoryPressureStatusChanged):
(WTF::MemoryPressureHandler::didExceedProcessMemoryLimit):
* Source/WTF/wtf/MemoryPressureHandler.h:
(WTF::MemoryPressureHandler::setMemoryPressureStatusChangedCallback):
(WTF::MemoryPressureHandler::setDidExceedProcessMemoryLimitCallback):
(WTF::MemoryPressureHandler::isUnderMemoryWarning const):
(WTF::MemoryPressureHandler::isUnderMemoryPressure const):
* Source/WTF/wtf/cocoa/MemoryPressureHandlerCocoa.mm:
(WTF::MemoryPressureHandler::install):
* Source/WTF/wtf/unix/MemoryPressureHandlerUnix.cpp:
(WTF::MemoryPressureHandler::triggerMemoryPressureEvent):
* Source/WTF/wtf/win/MemoryPressureHandlerWin.cpp:
(WTF::MemoryPressureHandler::windowsMeasurementTimerFired):
* Source/WebKit/WebProcess/WebProcess.cpp:
(WebKit::WebProcess::initializeWebProcess):
Canonical link: https://commits.webkit.org/275198@main
Canonical link: https://commits.webkit.org/274313.162@webkitglib/2.44
Commit: 25e4703314326cda79659dec3e4843263da30c32
https://github.com/WebKit/WebKit/commit/25e4703314326cda79659dec3e4843263da30c32
Author: Philippe Normand <[email protected]>
Date: 2024-04-26 (Fri, 26 Apr 2024)
Changed paths:
M Source/WebKit/WebProcess/Network/webrtc/LibWebRTCNetworkManager.cpp
Log Message:
-----------
Cherry-pick 275090@main (c62c74690915).
https://bugs.webkit.org/show_bug.cgi?id=269836
[WPE][GTK] Disable mDNS LibWebRTC support
https://bugs.webkit.org/show_bug.cgi?id=269836
Reviewed by Adrian Perez de Castro.
Disable mDNS address resolving for WPE and GTK ports, mDNS address
registration is implemented only
for the Mac ports, so resolving can work only for those, currently.
* Source/WebKit/WebProcess/Network/webrtc/LibWebRTCNetworkManager.cpp:
(WebKit::LibWebRTCNetworkManager::GetMdnsResponder const):
Canonical link: https://commits.webkit.org/275090@main
Canonical link: https://commits.webkit.org/274313.163@webkitglib/2.44
Compare: https://github.com/WebKit/WebKit/compare/bb9c461af9bf...25e470331432
To unsubscribe from these emails, change your notification settings at
https://github.com/WebKit/WebKit/settings/notifications
_______________________________________________
webkit-changes mailing list
[email protected]
https://lists.webkit.org/mailman/listinfo/webkit-changes
