How to solve the hard damage of Google Chrome eating memory?

Chrome has become the world’s most popular browser, but that doesn’t mean it’s perfect – at least in terms of resource use, it’s often overlooked. Especially when it comes to memory usage, Chrome’s strategy is often exclaiming that no matter how much memory you add to your machine, Chrome has a way to eat it up. How do you solve this problem? Let’s talk about it today.

The reason chrome is so memory-intensive is tied to its mechanics. Each Chrome tab enables a new process, which is responsible for rendering, scripting, and so on, and each process needs to take up a significant amount of resources. At the same time, even if you don’t cut the tab, it will still keep the page elements running in real time, so when Chrome turns on multiple tags, these tabs will occupy a lot of resources alone, and memory will be consumed.

How to solve the hard damage of Google Chrome eating memory?

Chrome’s mechanism is very memory-eating.

How do you solve the problem? The tab occupies the thread, which is the underlying mechanism of Chrome, and is difficult to change, so all you need to do to save Chrome’s memory is keep the background tabs out of active and the background tabs free up resources. In fact, Chrome plans to do just that in the new version, and one of Chrome’s development ideas is to reduce the JS wake-up timer for background tab pages so that pages in the background tabs don’t run unnecessary tasks, which can save a lot of resources.

However, this improvement on Chrome has not yet been applied to the current version. What to do? Similar effects can be achieved through third-party extensions.

The Great Suspender: https://chrome.google.com/webstore/detail/klbibkeccnjlkjkiokjodocebajanakg.

This is an old Chrome extension that freezes the back-office tabs. In the Chrome Store, the Great Suspender can be installed directly, while domestic users can also find the appropriate crx file installation directly through the search engine.

The great Suspender’s role is that it freezes the back-background tabs after a certain amount of time, pauses the pages in the tabs, and emptys resources. The Great Suspender is also very simple to use, after installation, the appropriate settings page will pop up, you can set in it for a long time after the tab can be frozen, for example, can be set to 1 hour, then the background tab if 1 hour inactive, will be frozen. In addition, you can also set do not freeze fixed, playing, input box with text and in use of the label, can be described in very detailed.

How to solve the hard damage of Google Chrome eating memory?

You can automatically freeze the background tab after a certain amount of time.

How to solve the hard damage of Google Chrome eating memory?

Some settingoptionoptions.

After the tab is frozen by The Great Suspender, browsing the tab needs to be reloaded, and by default, the page needs to be manually refreshed before you can continue browsing. However, The Great Suspender also offers the option to reload automatically, making it easier to reload when you browse a frozen tab. It is worth mentioning that this reload does not need to be done over the network, but uses the local cache, even if it is off-network, you can re-display the original page and go back to where it was previously viewed.

How to solve the hard damage of Google Chrome eating memory?

A frozen tab can actually be set to refresh automatically when you switch to a frozen tab.

Take a look at the effect of The Great Suspender. We used The System Task Manager for resource monitoring, and as you can see from the following comparison, Chrome’s memory was up to 1.2G before freezing the tab, and after freezing the background tab with The Great Suspender, there was only 670M left, and the results were immediate.

How to solve the hard damage of Google Chrome eating memory?

The memory-saving effect is still obvious.

Overall, The Great Suspender does solve the problem of too much Chrome memory. However, its experience is not perfect, freeze the label and then browse need to reload this, will interrupt the continuous browsing experience of the web page, and will consume CPU resources. However, until officials release a new version of improved resource usage, it’s still a great way to reduce Chrome’s memory footprint, and those who need it may want to give it a try!