Chrome Throttle Mania

About

For unknown reasons, Chrome developer team is being more and more obsessed with throttling.
Javascript code running in Chrome tabs might be throttled and this can have serious impact while using PowerSniper or other extensions.

Throttling is occuring after a given time lapse when Chrome window is hidden or iconized, preventing code from running more than once per minute.
You will then get a log message : 'For an optimal beheavior, please leave this Chrome window visible. (timer took 59s)' or so.

Workarounds described below may not work in near futur since they are changing behavior without notice.
Flags might disappear, command line flags might end having silently no effect.

Most of the time an opened web browser tab with a partially visible PowerSniper tab should be enough.
But beware of RDP closed session or desktop locked session. Also mind that beheavior is different on Windows 10, Windows 11 and MacOs.

Possible Workarounds

  • Preferred: activate 'Use Sound Trick' option.
    This will periodically emit a sound beep preventing though the web browser from throttling.
    If so, do not completely cut sound from your OS configuration panel.
  • Download and use (double click) this reg file (Windows users).
  • Set --disable-backgrounding-occluded-windows at Chrome command line (not sure if it works anymore).
  • Do not use Chrome! PowerSniper works on any Chromium core. Use the direct download link for this.
  • Leave you desktop session or RDP client opened.
  • Always leave a portion of browser extension screen visible.
  • Activate #temporary-unexpire-flags-m96 flag then disable #calculate-native-win-occlusion (not sure if it works anymore).