You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Sep 9, 2022. It is now read-only.
I suspect this might be caused by the browser's "Predict network actions to improve page load performance" setting. I suspect the browser may create/dispose of tabs internally which are never really rendered and thus never go through the chrome.tabs.onRemoved event, and as a consequence never removed from memory.
At this point the simplest way to address the issue is to have a janitor which find and dispose of stale page store entries.
The text was updated successfully, but these errors were encountered:
Ok, confirmed, if "Predict network actions to improve page load performance" is enabled, this will causes stale page store entries when searching a term in the search bar.
Have "Predict network actions to improve page load performance" enabled
Open new tab
Enter "allo" in address bar
Close tab
Open extension's background page and enter µBlock.pageStores in console
Result: there is a page store entry for http://www.allo.com/
It appears Chromium will automatically load the first link of result in an off-screen tab, which will never receive a tabs.onRemove() event, and as a consequence the page store entry (and all associated data structures) will occupy memory needlessly forever.
Need to fix ASAP, as I suspect that most users do not disable the "Predict network actions..." setting (I personally think everybody should disable it).
I suspect this might be caused by the browser's "Predict network actions to improve page load performance" setting. I suspect the browser may create/dispose of tabs internally which are never really rendered and thus never go through the
chrome.tabs.onRemoved
event, and as a consequence never removed from memory.At this point the simplest way to address the issue is to have a janitor which find and dispose of stale page store entries.
The text was updated successfully, but these errors were encountered: