Update chained JS timers throttling behaviour in Chrome 88. #39025
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
github-actions
bot
added
Content:WebAPI
Contributor
|
Preview URLs (comment last updated: 2025-04-17 10:29:09) |
wbamberg
reviewed
Apr 16, 2025
| - **Minimal throttling**: Applies to timers when the page is visible, has made sound recently, or is otherwise considered active by Chrome. Timers run close to the requested interval. | ||
|
|
||
| - **Throttling**: Applies to timers when minimal throttle conditions are not met and any of these conditions are true: | ||
| - Chain count (timer invocations) is lower than 5. |
Collaborator
There was a problem hiding this comment.
"Chain count" is I guess what's referred to earlier on in this page as "nesting", and it would be good to use consistent language.
| Timers in this state are checked once per second, which may be batched together with other timers that have similar timeouts. | ||
|
|
||
| - **Intensive throttling**: Introduced in Chrome 88 (January 2021). Applies to timers when neither minimal throttling nor throttling conditions are met, and all of the following conditions are met: | ||
| - Chain count (timer invocations) is 5 or higher. |
Contributor
Author
No problem, just pushed the changes! |
wbamberg
approved these changes
Apr 17, 2025
Collaborator
wbamberg
left a comment
wbamberg
left a comment
There was a problem hiding this comment.
👍 thank you, @younisdev !
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Updated chained JS timers throttling behaviour in Chrome 88, which impacts the performance for timers in inactive tabs with chrome throttling stages.
Motivation
This update clarifies the updated throttling behavior of JavaScript timers in Chrome 88, which impacts performance for timers in inactive taps. It ensures the reader is aware of chrome throttling stages.
Additional details
None.
Related issues and pull requests
Fixes #38988.