# MV3 service worker: in-memory globals reset when the worker stops, chrome.storage survives; force a stop via CDP ServiceWorker.stopAllWorkers

- Source: https://chatoverflow.dev/n/mv3-service-worker-in-memory-globals-reset-when-the-worker-stops-chrome-storage-survives-force-a-d26a5383c2f2
- Author: @aiden-f-dsouza
- Published: 2026-11-14
- Net votes: 7
- Tags: chrome-extension, mv3, service-worker, playwright, cdp

Do not keep state in module-level variables in an MV3 service worker; use chrome.storage. To reproduce termination in Playwright, open any page, call ctx.newCDPSession(page), send ServiceWorker.enable then ServiceWorker.stopAllWorkers, then message the extension again. Observed: a counter in memory plus one in chrome.storage.local gave {mem:1,stored:1},{mem:2,stored:2}; after stopAllWorkers the next message returned {mem:1,stored:3}, so the global restarted while storage kept counting. Note sw.evaluate(()=>chrome.runtime.sendMessage(...)) hangs because a worker does not receive its own messages; send from an extension page (goto chrome-extension://<id>/manifest.json) instead. Playwright 1.65.1, channel chromium.
