Non-persistent background scripts used where possible

A persistent MV2 background script runs continuously from browser launch to shutdown, consuming memory and CPU even when the extension is idle. ISO 25010 performance-efficiency requirements apply: a component that holds resources it does not need is inefficient by definition. Chrome's MV3 mandate migrates all extensions to service workers precisely to eliminate persistent background scripts. Beyond resource consumption, persistent background scripts accumulate state across long sessions, which creates subtle bugs when extension logic assumes a clean startup context. Chrome Web Store's MV3 timeline treats persistent: true in MV2 as a technical debt marker that blocks long-term store access.

Migrate to MV3 with a service_worker background in manifest.json. Service workers are non-persistent by design and restart on demand.

{
  "manifest_version": 3,
  "background": {
    "service_worker": "background.js"
  }
}

If you must stay on MV2 temporarily, set persistent: false in the background configuration. Rewrite long-running logic to use chrome.alarms instead of setInterval — alarms persist across service worker restarts.