Ladies and gentlemen, please note: Chrome will launch doing something to permanently open tabs. Chrome version 110 is rolling out now, and on Windows, macOS, and Linux, this release comes with a new “memory saver” feature that is automatically enabled. We first wrote about this in December when it appeared in Chrome’s nightly build “Canary Channel”, but now the feature is rolling out to all users.
Chrome has a reputation for hogging RAM, and Google seems to think the best way to combat this is to automatically shut down tabs when they’re “inactive.” Google’s description of the feature states, “When a tab is destroyed, its title and favicon continue to appear in the tab strip, but the page itself disappears, as if the tab had been closed normally. When you visit the tab again, the page will automatically reload.” Google says this technique reduces Chrome’s memory usage by “up to 40 percent.”
Google has some use cases excluded from this feature, as outlined on the support page.
Some computer settings and activities may prevent tabs from deactivating.
- Active audio or video (playback or call)
- screen sharing
- page notification
- active download
- partially filled form
- Connected device (USB or Bluetooth)
-
The “chrome://discards/” page allows you to manually discard tabs for testing purposes.
Ron Amadeo
-
I have no idea what this graph is trying to convey. However, clicking on the little balls reveals details on different pages.
Ron Amadeo
-
Look at it! If you open a new tab in another window and load Feedly, the graph will look like this:
Ron Amadeo
Type “chrome://discards” in the address bar to see the developer UI that controls the new tab discard feature and see how all this works. The Destroy tab shows the status of all tabs and the Actions column on the right contains an Emergency Destroy link to manually destroy any tab for testing purposes.After blasting some of my favorite sites and seeing how they reacted, here’s[グラフ]I highly recommend checking out the tab (there’s a GIF in the gallery above). you are using chrome.
From this page, you can infer Chrome’s tab-destroying behavior. Tabs that are in front cannot be dismissed manually. You have to click another tab, put the window in front of Chrome, or minimize Chrome to discard the tab. Perhaps that’s how the auto-destroy feature works too. A page in serious unsaved state can be a real problem. If you dump a bunch of text into WordPress and try to close the tab with the normal close button instead of closing, you’ll get a popup about unsaved changes. Asking if they want to leave the site may prevent them from losing a lot of work. Chrome’s New Tab Discard feature causes Chrome to discard unsaved text as if it never happened. Some sites, such as Gmail, do a good job of dealing with this by following Google’s recommendations and autosaving draft text when tabs are moved to the background.
how to turn off
-
If a tab has been shut down, you will see this message when you return to that tab.
-
New “Performance” settings and how to set them.
The good news is that you can control all of this. Consumer controls for memory saver can be found at ‘chrome://settings/performance’. If you care about UI, menu,[その他のツール],[パフォーマンス]Click You can either turn off this feature completely or add the site to the list of “Always keep these sites active”. Google has detailed instructions on how exclusion parsing works on their support page, but it supports everything you’d expect: subdirectories, wildcards, specific subdomains, etc. Personally, I need to add an Ars Technica WordPress instance. It’s a nightmare for every writer as it can lead to loss of unsaved article text.
In addition to memory saving features, this version of Chrome also features an “Energy Saver” mode for laptops that reduces video and scrolling frame rates to reduce tab power usage when battery is low. Suppress. The controls for that feature are on the same Performance tab.
