Status: Available Owner: ---- Labels: Type-Feature Pri-2 OS-All Area-Misc Size-Medium
New issue 18593 by j...@chromium.org: Improve windowless plugins memory usage http://code.google.com/p/chromium/issues/detail?id=18593 There are some low hanging fruit for reducing windowless plugin memory usage which were introduced when we switched to asynchronous painting (see the last section in http://dev.chromium.org/developers/design- documents/plugin-architecture) The transport DIB is kept allocated all the time. We can switch to a model just like the browser <> renderer where it's allocated only when it's needed, and use a cache that times out often and releases the memory. This would release the plugin memory for background tabs. For transparent plugins, we also keep a DIB of the background, so that the plugin composites over the data. We keep this around all the time, but we can throw it out when the page is not in the foreground and painting isn't happening. We'll then need to do synchronous painting the first time the plugin is visible, which is ok (the killer is scrolling, but we can optimize this case by keeping the DIBs around for foreground pages). Lastly, we keep the backing store of the plugin around always, but again we can remove it and paint synchronously the next time, if the page is not visible. -- 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 -~----------~----~----~----~------~----~------~--~---
