The extension cannot communicate with the app's page directly, that's why we relay the changes through content script to the extension's background script, where we're recreating the lifted store with some additional features. Basically if the client store state has 10MB, we're adding at least another 10MB in the extension's process. From extension's windows we're just accessing this object through getBackgroundPage. However, from devpanel it wasn't possible to access it, so we had to send it there (adding another 10MB in that case). In recent versions Chrome added support for chrome.runtime.getBackgroundPage from devpanel. So we can take advantage of it consuming up to 50% less memory and boosting the performance.

For Firefox and Electron it's still not available, so we'll keep old scenario there.