# Google Chrome & Memory Consumption

**URL:** https://boards.straightdope.com/t/google-chrome-memory-consumption/707626
**Category:** Factual Questions
**Created:** [December 19, 2014, 12:16am UTC](https://boards.straightdope.com/t/google-chrome-memory-consumption/707626 "2014-12-19T00:16:31Z")
**Posts on this page:** 2
**Page:** 1

<div class="post-metadata">

### Author: ![OldOlds](https://avatars.discourse-cdn.com/v4/letter/o/a3d4f5/32.png) [@OldOlds](https://boards.straightdope.com/u/OldOlds)
#### Post date: [December 19, 2014, 12:16am UTC](https://boards.straightdope.com/t/google-chrome-memory-consumption/707626/1 "2014-12-19T00:16:31Z")

</div>

Hi Folks

I am not very knowledgeable about computers, so I wondered if something has happened with Chrome.

Recently, as in the last few weeks, when I open more than a couple of tabs in Chrome, my computer becomes maddeningly slow. Performance monitor indicates that Chrome is consuming massive amounts of memory. Right now I have three tabs open (SD, Gmail, and TTAC) and it’s eating up 1.3GB!

This never used to be an issue. I see no indication of malware or any such.

Has Chrome changed recently? Did it lose it’s roots as a small, quick, and simple browser?

I’m not here to bitch, rather I would like to understand if there’s an explanation here.

I just opened Firefox and opened the same three tabs, and the total consumption per Task Manager is 369MB

---

<div class="post-metadata">

### Author: ![engineer\_comp\_geek](https://sea3.discourse-cdn.com/straightdope/user_avatar/boards.straightdope.com/engineer_comp_geek/32/504_2.png) [@engineer\_comp\_geek](https://boards.straightdope.com/u/engineer_comp_geek)
#### Post date: [December 19, 2014, 12:26am UTC](https://boards.straightdope.com/t/google-chrome-memory-consumption/707626/2 "2014-12-19T00:26:17Z")

</div>

Chrome developed a memory leak or some kind of memory problem about five or six months ago. I don’t use Chrome and don’t keep up with its news so I don’t really know the details of it and I have no idea if it has been fixed yet or not. If nothing else, you might try updating it to the latest version in the hope that a recent patch fixed it.
