The latest Chrome 133 (developer preview version first), the official revealed that it will introduce a new power-saving mode function that “just as the name suggests” will actively freeze (Freezing) background pagination. Continue reading Google Chrome 133 introduces a new “freeze” function to save resources and maintain working status.
▲Photo source of this article: Google
Google Chrome 133 introduces a new “freeze” function to save resources while maintaining working status
In order to get rid of the reputation of resource-hogging, Google began to gradually push the memory/power saving function last year to more actively release memory resources from the pages you are not currently using. Previously, it has further evolved memory management, bringing proactive warnings and even allowing users to customize Chrome’s memory method logic based on the computer environment and usage scenarios.Performance issue alert“New settings.
Coming to the latest Chrome 133 (developer preview version first), the official revealed that it will introduce a new power-saving mode function that “just as the name suggests” will actively freeze (Freezing) background pagination.
After seeing this, many people will probably want to ask immediately, how is it different from the previous discarding methods that pause and release system resources for background paging that is not in use? According to the official statement, this function is different from unloading paging from the memory. It will resume the execution of tasks when returning to paging (that is, if it freezes, it can be unfrozen~), and the previous execution state will not be lost.
This feature also has many triggers. First of all, it currently requires power saving mode to be enabled. The freeze feature will also only activate for paging that exceeds a certain CPU usage threshold and has been paused for more than 5 minutes.
In addition, for things like chat or email services that require instant notification and calendar services that require event notification. There are also audio, video conferencing, and web pages that need to control external devices, which will be within the exceptions of this new feature. According to the official description:
在節能模式下凍結：當省電模式啟用時，如果其中任何同源框架的子群組超過 CPU 使用量門檻，Chrome 就會凍結已隱藏且靜默超過五分鐘的「瀏覽內容群組」
This feature will pause the execution of functional tasks such as event handlers (Event Handlers), timers (Timers), and Promise resolvers (Promise Resolvers). This can more effectively extend the battery life of your device. Regarding how to avoid your webpage being included in the scope that will be frozen, the official has listed several key points (machine-translated, please read the original URL of the reference link for details):
・避免使用計時器來定期檢查狀態變化。
。使用 IntersectionObserver 偵測元素何時進入視口。
。使用 ResizeObserver 監測元素大小變化。
。透過 MutationObserver 或自定義元素生命週期回呼處理 DOM 變化。
・考慮使用 Web Sockets、伺服器推送事件 (SSE)、推播訊息或 fetch streams，取代輪詢伺服器的方式。
・對於音訊或視訊變化，使用timeupdate和ended事件。
via:Neowin|Reference materials:Chrome for developers
Further reading:
Source: KOCPC Chinese