Chrome's reputation for hogging memory is more myth than problem

Chrome's reputation as a memory hog is more internet joke than real problem, according to a new Engadget explainer. Yes, Chrome uses a lot of RAM, the short-term memory a computer uses to run things quickly. But that is mostly on purpose, and it is not a sign that something is broken.

Why Chrome uses so much

Websites today work more like apps than simple pages. People also keep many tabs open and run several extensions in the background. Browser makers have to choose: share memory across tabs to save RAM, or give each site its own process, which costs more memory but keeps things fast and stable. Chrome picks the second option, as many other browsers do.

What you get in return

• Speed: each site runs in its own space, so browsing stays responsive.
• Stability: one crashed site does not take down the whole browser and your 20+ tabs.
• Security: a malicious page can't easily peek at your banking or email tab.

Some of the extra memory is the price of that wall between tabs. The article argues most people would gladly pay it.

Unused RAM is wasted RAM

Many people think memory use should be as low as possible. The article says the opposite: memory exists to hold what you want running smoothly. PCMag says 8GB of RAM should be fine for most general-use PCs, several times what a single browser typically needs.

What to do if Chrome feels slow

Do not judge by the memory number alone. Press Shift + Esc in Chrome to open its Task Manager and look for a tab or extension that keeps growing. That pattern can point to a memory leak, which is when a program grabs memory and never gives it back.

• Turn on Memory Saver under Performance in settings. It puts idle tabs to sleep and is now available to everyone.
• Add sites that should never sleep, such as the one playing your music.
• If nothing is growing, leave Chrome alone. Look at a nearly full drive or a slow connection instead.
• Restarting the browser is a good first step.

Other browsers take different routes. Edge, built on the same Chromium foundation, uses sleeping tabs and Energy Saver. Firefox shares processes across tabs and unloads tabs when memory runs low. Neither is a cure, since using far less memory would mean giving something up.