Starting with version 97, Chrome implements a usage limit on the APIs we rely on for filmstrip, screenshots, and calculating the Render Start metric. The API now allows only two screenshot captures per second. Google implemented this limit to improve the performance of the browser when users have extensions relying on this API.
The limit is hardcoded in Chrome and cannot be changed by any switch or configuration. Our engineering team is looking at a different mechanism to gather screenshots, but that will take some time to investigate, code, and test.
For now, the following will be impacted:
- Filmstrip frames will not be any more frequent than every 500ms. (It is recommended to set the frequency of filmstrip to 800ms or above, which should produce consistent results)
- The Render Start metric will not be accurate, and you need to rely on First Paint
- There may be cases where there is a filmstrip, but not a screenshot because of the conflict. (Setting the frequency of filmstrip to every 1+ second will help)