Issue 35805 in chromium: Each tab takes up 40MB of memory

2 views
Skip to first unread message

chro...@googlecode.com

unread,
Feb 15, 2010, 5:11:34 PM2/15/10
to chromi...@chromium.org
Status: Unconfirmed
Owner: ----
Labels: OS-Linux Area-Undefined Type-Bug

New issue 35805 by mats.ahlgren: Each tab takes up 40MB of memory
http://code.google.com/p/chromium/issues/detail?id=35805

Chrome Version (from the about:version page): 4.0.249.43
Is this the most recent version: yes?
OS + version: Suse 11.2
CPU architecture (32-bit / 64-bit): 64
Window manager: Compiz
Behavior in Linux Firefox: worse

What steps will reproduce the problem?
1. memory manager reports that almost all tabs use 40-50megabytes of
memory. this can be very bad with 40 tabs open

This might be due to the fact that I have set this computer not to page to
disk, but rather into memory. Nevertheless I would hope some form of
compression could be used, e.g. if Chrome is using some sort of canvas,
then perhaps the canvas could be compressed based on the frequency of DOM
redraws, or it could be transparently compressed in memory (e.g. grouping
every 16x16 pixels, compressing, then hashing identical blocks).

--
You received this message because you are listed in the owner
or CC fields of this issue, or because you starred this issue.
You may adjust your issue notification preferences at:
http://code.google.com/hosting/settings

chro...@googlecode.com

unread,
Feb 16, 2010, 8:17:12 AM2/16/10
to chromi...@chromium.org

Comment #1 on issue 35805 by ev...@chromium.org: Each tab takes up 40MB of
memory
http://code.google.com/p/chromium/issues/detail?id=35805

The most recent version is
Google Chrome 5.0.322.2 (Official Build 38810) dev

Can you try that?

chro...@googlecode.com

unread,
Feb 23, 2010, 1:19:34 AM2/23/10
to chromi...@chromium.org
Updates:
Status: WontFix

Comment #3 on issue 35805 by tony.chromium: Each tab takes up 40MB of memory
http://code.google.com/p/chromium/issues/detail?id=35805

Did you actually try opening 40 tabs? Chrome should start sharing
processes after
some point, so it shouldn't actually use 40 separate renderer processes.
If you
actually see 40 distinct processes, that sounds like a bug.

I'm not sure this bug is actionable. Here's an example of other memory
bugs, most of
which are calling out specific areas to be improved upon:
http://code.google.com/p/chromium/issues/list?q=label:Memory

If you have a specific idea on somewhere we should try to save on memory,
please
file a bug about it.

chro...@googlecode.com

unread,
Aug 9, 2010, 5:47:33 AM8/9/10
to chromi...@chromium.org

Comment #4 on issue 35805 by mats.ahlgren: Each tab takes up 40MB of memory
http://code.google.com/p/chromium/issues/detail?id=35805

On the latest version (6.0.458.1 dev, same system setup as above), Chrome
is having even worse memory issues:

- Open up program, no pages loaded: about:memory says Chrome is taking 100MB
- Open up a single tab from amazon.com: about:memory says Chrome is taking
~175MB
- Open up 7 more tabs from amazon.com: about:memory says Chrome is taking
~555MB
- Open up 20 copies of this bug report page: no noticeable change in memory
- Open up 10 copies of bbc.co.uk: not bad, Chrome is only now taking
~1.02GB of RAM
- Open up 5 copies of gmail: Chrome is now taking ~1.4GB of RAM total

I can only conclude that each tab of a complicated page contributes about
50MB to the total memory of Chrome.

Additionally today, I noticed that a single tab of Gmail was taking up an
*entire 1GB* of memory all by itself.

I am afraid that, as a bug reporter, I am insufficiently aware of Chrome's
internals that I can guess which of the linked bugs this may be related to.
=) All I can offer is a report of the problem.

Reply all
Reply to author
Forward
0 new messages