Active resource loading counts reached to a per-frame limit while the tab is in background. Network requests will be delayed until a previous loading finishes, or the tab is foregrounded. See https://www.chromestatus.com/feature/5527160148197376 for more detailsand unexpectedly found 57 of this west?
what"s wrong with this? This is found on my own web site. What is it? is it written?
in the Google Chrome 57 version published on March 14, 2017, in order to extend the battery life of notebooks, a limit on Javascript timers was added. The original setting is up to one time per second, but now the limit is more stringent. For tabs that are not displayed in the foreground, directly limit the use of CPU to no more than 1% of a kernel. Only when you switch this tab back to the foreground can it work properly. This is the meaning of the above line.
For more information, please see here .if you want to remove this restriction, you can type chrome://flags, in the browser's address bar and find Throttle expensive background timers, to disable it.
Previous: Parsing and processing combined xml data, the solution must be appreciated
Next: Three.JS makes a large number of different objects, how to ensure the number of frames and memory