-
Notifications
You must be signed in to change notification settings - Fork 2.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Clear cache when idle #869
Comments
+1 This in the popular browsers is usually a separate feature provided by an extension to make the browser state more responsive again. It's brilliant that you're going to implement it as just a random feature as a privacy concern but could potentially have other benefits to a user as well. Hypothetically, if a user had 80 tabs open which resulted in 2+GBs of physical memory and a bit of swap being used-up, could your implementation of pro-active purging reduce this as though the browser was restarted and the 80 tabs were loaded again from bookmarks? |
+1 the only reason I can't leave firefox is that I cannot install cookie auto-delete on my mobile. |
Cache provides performance improvements, but generally doesn't store state that matters to users. However, it's a great side-channel for setting state on a client machine. We could pro-actively purge cache state from tabs which have been idle for a while to reduce the scope of cache-based attacks.
The text was updated successfully, but these errors were encountered: