Hi!
I forgot to mention this issue, thank you for bringing it up.
Background throttling is disabled whenever something that is
considered real time, like audio, or could potentially time out, like
web sockets, is present on he page, including iframes.
To both prove to myself that these mechanisms
Yes, there are related telemetry probes, but I've recently convinced
myself that they won't be able to clearly detect budget throttling.
The probe is TIMEOUT_EXECUTION_BG_MS, and the reason for it not
working is that it accumulates execution over one second, which just
happens to be the time of the
Thanks a lot for working on this, it sounds awesome! Can I ask if there are
any related telemetry probes that will be used later on to evaluate the
results and maybe tune these constants? Do you plan to expose any of these
parameters to web extensions?
Gabor
On Thu, Oct 5, 2017 at 5:27 PM, Andrea
Hi all!
After Bug 1377766 lands, we will increase the amount timeouts
executing in background tabs are throttled, based on an execution
budget. This budget is continuously regenerating, and is decreased
when timeouts execute. If the budget becomes negative, timeouts will
not be allowed to run unti
4 matches
Mail list logo