[Coda]

Okay, I've looked a little closer at that picture.

First off, that's not 100k. That's 100,000k, or 100 MB. 100MB isn't quite so absolutely tiny, but even on a machine with only 1GB of RAM (and note that Windows 7 64-bit has 4GB as the minimum recommended amount) that would only 10% of your system RAM. On your 8GB machine, that's only 1.2%.

Second, that's not physical memory; that's process memory. The memory corresponding to parts of the program that you're not currently using (for example, background tabs) can be stored on your hard drive instead of in your physical RAM if other programs, processes, Chrome tabs, or services need it. When this happens, your total physical RAM in use won't appear to change -- you'll still be at 90%+ usage, but everything will still work. It'll be a little bit slower for a moment when you do go and use the stuff that's been saved to disk, but once it's been reloaded (and something else is saved to disk in its place) you won't notice the difference.

Long story short: Chrome, with the master process and all of the tabs combined, is using up less than 350MB of RAM (that is, somewhere around 4.2% of your installed memory), and some of that may not even be physical RAM. Your computer is fine, Chrome is fine, and you shouldn't be seeing any trouble at all even on computers with half the specs of yours.

Edit: I suppose you could have more tabs open than show up in the process list there, but those would all be less than 11MB each, so you'd have to have literally hundreds of tabs open for Chrome itself to be the problem.

Odds are there's something else besides Chrome eating up memory, and since it's not showing in that list it's probably a system service instead of an application.