Guide

Guide

Fix 'Service Worker' High CPU Usage in Chrome

Fix 'Service Worker' High CPU Usage in Chrome

Feb 6, 2026

Feb 6, 2026

Modern websites install "Service Workers", scripts that run in the background even after you close the tab (to handle push notifications or offline sync). Often, these workers get stuck in a loop, appearing in Task Manager as "Service Worker: https://youtube.com" consuming 10-20% CPU constantly.

Modern websites install "Service Workers", scripts that run in the background even after you close the tab (to handle push notifications or offline sync). Often, these workers get stuck in a loop, appearing in Task Manager as "Service Worker: https://youtube.com" consuming 10-20% CPU constantly.

The Manual Fix

The Manual Fix

  • Unregister Workers: Go to chrome://serviceworker-internals/, find the buggy site, and click Unregister.

  • Block Background Sync: Go to Settings > Privacy > Site Settings > Background Sync and disable it for suspicious sites.

  • Hard Reload: Open the site and press Ctrl+Shift+R to force an update of the worker file.
  • Unregister Workers: Go to chrome://serviceworker-internals/, find the buggy site, and click Unregister.

  • Block Background Sync: Go to Settings > Privacy > Site Settings > Background Sync and disable it for suspicious sites.

  • Hard Reload: Open the site and press Ctrl+Shift+R to force an update of the worker file.
  • The Automated Fix

    The Automated Fix

    SuperchargeBrowser creates a boundary. Our Script Control module can throttle the execution context of these workers. Furthermore, our Privacy/Blocking engine often blocks the registration of Service Workers from tracking domains (like push notification spammers) entirely.

    SuperchargeBrowser creates a boundary. Our Script Control module can throttle the execution context of these workers. Furthermore, our Privacy/Blocking engine often blocks the registration of Service Workers from tracking domains (like push notification spammers) entirely.

    Technical Root Cause Analysis


    Service Workers are intended to be ephemeral (wake up, do task, sleep).


    • The Bug: Poorly coded workers keep a "Keep-Alive" connection open to the server, polling for notifications every second.

    • The Impact: This prevents the CPU from idling.

    • The Fix: By blocking the network requests associated with these polls, SuperchargeBrowser forces the worker to idle, saving your battery.

    Technical Root Cause Analysis


    Service Workers are intended to be ephemeral (wake up, do task, sleep).


    • The Bug: Poorly coded workers keep a "Keep-Alive" connection open to the server, polling for notifications every second.

    • The Impact: This prevents the CPU from idling.

    • The Fix: By blocking the network requests associated with these polls, SuperchargeBrowser forces the worker to idle, saving your battery.