Bug #57808 ,  #57594 , and  #56627  are definitely dupes of this report.

There are 2 bugs regarding the composite changes which are probably the more technically detailed version of this bug as well as the dupes.

However, I too am seeing this issue.

I'm seeing this too on Linux 7.0.536.2 (Official Build 60818) dev

It's the GPU process that eats up all the memory.

I'm not at all familiar with the GPU stuff in chrome, adding a few people.

Anthony, I'd consider this a release blocker. WDYT?

Doesn't happen on mac.

happens to me too using trunk.
If it matters, that's with an nVidia 9600GT running with the nvidia-current driver (260.19.06).

work-around: --disable-accelerated-compositing

I'm seeing this on 7.0.517.36, and on earlier versions with --enable-accelerated-compositing.
I have also been seeing the same symptom for quite some time with some WebGL demos at Khronos (without compositing).

Nvidia drivers 260.19.06, card Quadro NVS 130M, xorg-server 1.9.0.901

happens 8.0.551.0 (62097) Ubuntu 10.10 nvidia 8400 with nouveau 3D drivers.
work around helps

Changing milestone from Mstone8 to Mstone-9

Chrome Version (from the about:version page): 7.0.540.0 (Developer Build 61020) Ubuntu 10.04
Is this the most recent version: yes
OS + version: Ubuntu 10.04
CPU architecture (32-bit / 64-bit): 32-bit
Window manager: Gnome
URLs (if relevant): maps.google.com
Behavior in Linux Firefox: Normal: No increase in memory usage.
Behavior in Windows Chrome (if you have access to it):

What steps will reproduce the problem?
1. Go to maps.google.com
2. Switch to satellite view
3. Zoom in and then out very rapidly

What is the expected result?
The map will zoom in and/or out, and display the new map.

What happens instead?
The memory usage climbs, rapidly exhausting about 1.5 gigabytes of RAM in about 10 seconds, causing Chromium and the entire system to barely function.

Please provide any additional information below. Attach a screenshot
and backtrace if possible.

The screenshot below shows the resource utilization while this is happening.

This issue has been closed for some time. No one will pay attention to new comments.
If you are seeing this bug or have new data, please click New Issue to start a new bug.