How to fix severe memory leakage in Google Chrome.
Sometimes, when I really get into things, I couldn’t stop until I find a solution. In a preivious article, I pointed out Google Chrome’s possibilities about being the fastest web browser yet, given the right configuration. Then I talked about Google Chrome’s memory leak. Here’s the part where I tell you a solution.
First, let us talk about memory leaks.
Chrome Memory Leak is annoying
Memory leaks are simple. It is usually accompanied by terrible slowdown on the application experience memory leakage, and most of the time, the entire machine. If you are lucky, it gradually slows until it freezes, hangs, or crashes. That’s what a memory leak is.
Google Chrome is indeed a fast web browser, however, it has some serious issues with memory leakage. In idle mode, Chromium tabs already use up to 100MB of physical memory. When you open more tabs, the memory commit increases. The problem is that when you close a tab, the memory allocated to it isn’t released by the application. It causes the memory leak.
Why is there Memory Leak in Chrome?
I ran a thirty minute test on Google Chrome and, not to brag, I immediately knew what was causing the leak (or at least, I got some clues). On the downside, it seemed that the memory leakage is vital to Chrome, as though the browser relies heavily on it.
Technically, the memory leak is the thing that makes Google Chrome much faster than Opera. Opera saves the browsing history along with your cookies, recent graphics, media, etc. to virtual memory more than what is necessary.
Cache in Virtual and Physical Memory
When a webpage in Opera requests for data, Opera checks virtual memory—space on hard disk that functions much the same way as physical memory, only slower—and if the data is present, there’s no need to request it from the server. The process saves time, bandwidth, and cpu power.
Back to Chromium Memory Leaks
In a nutshell, memory leakage is inevitable to Google Chrome. And after all that boring stuff, here’s the fun part. The actual fixes:
Chromium Memory Leak Fixes
Since memory leaks are vital to Chromium applications, it’s safe to say Google developers won’t be solving that problem for us soon. So we improvise.
Chromium Memory Leak Fix # 1
Restart Chrome. Sorry, but that is the simplest possible way. When you close Chrome, it releases the memory. Restart the browser, and do it all over again. Simple.
But that’s a hassle, so here’s another option:
Chromium Memory Leak Fix # 2
Clear History. It has certain dependencies, though. Cleaning your browsing history and cache in Google Chrome is as simple as pressing CTRL+SHIFT+DELETE on your keyboard. However, you have to make sure you have closed all tabs except one, a page called “about:memory.” It could also be any blank webpage or a new tab so the Chrome window does not close. Besides, “about:memory” really helps.
To summarize that, close all tabs, open “about:memory” by typing it into the address bar, then press CTRL+SHIFT+DELETE.
At the about:memory page, you should notice a significant drop in memory usage after deleting history and cache. Chrome should ease up, however, in order to load pages the browser must contact the server again.
Still, that is too complicated and tiresome, so here’s another one:
Chromium Memory Leak Fix # 3
Extensions. Here are some great Chrome extensions that helps you automate the job.
Simply click “x” button to clear history.
Instead of typing in “memory:about” on the address bar, you can just click the blue icon.
All CPU Meter
This is a Windows 7 Sidebar Gadget that works like Task Manager, to help monitor your CPU usage.