High Resolution Time

[uazo]

see https://w3c.github.io/hr-time/#sec-privacy

• kDisableHighResTimer
• Issue 1153139: Coalesce delayed wake ups
• 4652282: [task] Tweak effect of AlignWakeUps/ExplicitHighResolutionTimerWin | https://chromium-review.googlesource.com/c/chromium/src/+/4652282
• 3879883: [task] Less precise dom timer | https://chromium-review.googlesource.com/c/chromium/src/+/3879883
• Timer Coalescing and Semantics https://docs.google.com/document/d/1OjZoHNvn_vz6bhyww68B_KZBi6_s5arT8xMupuNEnDM/edit#
• Issue 1267874: There should exist base/ timers that do not cause high Idle Wake Ups, i.e. low-res timers https://bugs.chromium.org/p/chromium/issues/detail?id=1267874

[uazo]

special attention to https://github.com/uazo/bromite-buildtools/issues/291

turnstile (could) perform a performance check for something I have not yet fully understood, but it is related to the performance api that this issue would like to camouflage. the only thing I understood was that this is how they verify that the javascript debugger is open (because some API seem to be deactivated in case the profiler is active, for example).

Since their code is minimised, I can't really understand what it is doing, but I could think of a way to reconstruct the blink/v8-side activity.