Status: Unconfirmed
Owner: [email protected]
Labels: Type-Bug Pri-2 OS-All Area-Misc

New issue 6713 by unknown.unit: Flash Plugin consuming ever greater memory
http://code.google.com/p/chromium/issues/detail?id=6713

Chrome Version       : 2.0.157.0 (Developer Build 8165)
URLs (if applicable) :  
http://www.marketingpixels.com/articles/education/proper-english-grammar-
is-important-for-businesses.html
Other browsers tested:
   Add OK or FAIL after other browsers where you have tested this issue:
      Safari 3:
     Firefox 3: Appears to be OK (possibly needs longer testing to confirm)
          IE 7:

What steps will reproduce the problem?
1. open supplied URL
2. Open Chromium task manager
3. Watch Flash Plugin memory usage climb

What is the expected result?

Memory should not keep climbing

What happens instead?

Memory climbs as long as window is maximized

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

It seems that minimizing the window or placing it in the background
substantially slows the ramping up of memory.

On bringing the window back into the foreground focus it seems for a while
that the memory won't begin climbing again, but after a while it starts and
will not stop again until the window is no longer in focus.

The Flash Plugin was using 800mb of memory when I checked it earlier.
Closing that one single page released all but about 38mb of that (the rest
is obviously for other open pages.)

Although I cannot see the memory usage of the flash plugin in FF3, Windows
task manager reports just under 70mb total ram and 55mb total page file
used by FF3 after the page has been open for a while without indication of
increasing memory use.

I cannot believe the flash on that page needs all that memory, but that
doesn't mean this is necessarily a bug in Chromium.  If it is not a
Chromium bug, could we make this a feature request for a (possibly user
defined) memory limit for the flash on any page?  Even if this means the
flash stops working on that page, if you make it user defined then anyone
who simply must have that flash working can switch it off.

This problem is the first time I have experienced the memory related
slowdowns I have so often with FF (the main reason I sing the praises of
Chrome/Chromium to others) and it was very frustrating until I found out
which page caused the problem.

--
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

--~--~---------~--~----~------------~-------~--~----~
Automated mail from issue updates at http://crbug.com/
Subscription options: http://groups.google.com/group/chromium-bugs
-~----------~----~----~----~------~----~------~--~---

Reply via email to