Report (+solution) for: Uncaught (in promise) Error: Extension context invalidated.

Describe the bug

In Browser Extensions page:
Vimium 2.3 => Errors:
Uncaught (in promise) Error: Extension context invalidated.

To Reproduce

1. Use vimium on any page
2. Reload vimium extension
3. Switch back to a page where vimium has been used before reloading
   ...the error is generated when the input focus activates some invalidated content script.

Solution

content_scripts/vimium_frontend.js

async function checkIfEnabledForUrl() {
    //vvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvv
    if( extensionHasBeenUnloaded() ) {
        console.log("handling 'Extension context invalidated' error");
        return;
    }
    //^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
    const promises = [];
    promises.push(chrome.runtime.sendMessage({ handler: "initializeFrame" }));
    (...)
}

Browser and Vimium version

• Vimium 2.3
• Chromium: 139.0.7258.158
• Windows 10

Open content_scripts/vimium_frontend.js and inspect checkIfEnabledForUrl(); first reproduce the issue by reloading Vimium, then switch back to a previously used page. Done means the invalidated context no longer produces the reported uncaught promise error.