4 ms·
https://developers.google.com/web/updates/2015/09/tab-discarding?hl=en https://developers.google.com/web/updates/2015/09/tab-discar...
by Sarkie 10y ago
https://developers.google.com/web/updates/2015/09/tab-discarding?hl=en https://developers.google.com/web/updates/2015/09/tab-discar...
- afsina 10y agoAlso, https://docs.google.com/document/d/1thLjq-PYoKWaM_ODDZjojr9VRG6uGnxeL86EaSzYL5k/edit https://docs.google.com/document/d/1thLjq-PYoKWaM_ODDZjojr9V...
- afsina 10y agoAFAIK this is part of the TRIM project in Blink, They have some memory related goals listed here: https://docs.google.com/spreadsheets/d/17wW-YosF8tlEwn45eZ4delXWPDfWG70vmG-Gnc-63ro/edit?pref=2&pli=1#gid=1135956485 https://docs.google.com/spreadsheets/d/17wW-YosF8tlEwn45eZ4d...
- Sarkie 10y agoBrilliant, thanks for these links!
- alimbada 10y agoI think this feature would be much more useful if, instead of waiting for the system to run low on memory, I could define a memory usage threshold at which Chrome starts discarding tabs.
- scholia 10y agoAgreed. It would also be nice to limit the number of separate processes that Chrome uses. It's interesting to compare RAM/resource usage of a blank page in Google Docs in Chrome with a lightweight program such as Microsoft Word ;-)
- ikeboy 10y agoI don't see any such flag, and about:discards and chrome://discards/ don't work. Has the feature been dropped in Chrome 50, or was it just never implemented for Linux?