[chromium] Limiting render surface texture manager memory to 0 when contentsMemoryUse...
authorcommit-queue@webkit.org <commit-queue@webkit.org@268f45cc-cd09-0410-ab3c-d52691b4dbfc>
Thu, 17 May 2012 20:04:08 +0000 (20:04 +0000)
committercommit-queue@webkit.org <commit-queue@webkit.org@268f45cc-cd09-0410-ab3c-d52691b4dbfc>
Thu, 17 May 2012 20:04:08 +0000 (20:04 +0000)
commitf7136fda93cfe3ad27cbd0d23a4a87fcc34dbf9b
tree885dc22799803d8cbd2c33eee9ee695703fa3c48
parent7298e636f88c888c462dc0acb3e3b3f0e5871a3e
[chromium] Limiting render surface texture manager memory to 0 when contentsMemoryUseBytes is large.
https://bugs.webkit.org/show_bug.cgi?id=86764

Patch by Michal Mocny <mmocny@google.com> on 2012-05-17
Reviewed by Adrienne Walker.

* platform/graphics/chromium/LayerRendererChromium.cpp:
(WebCore::LayerRendererChromium::beginDrawingFrame):

git-svn-id: http://svn.webkit.org/repository/webkit/trunk@117485 268f45cc-cd09-0410-ab3c-d52691b4dbfc
Source/WebCore/ChangeLog
Source/WebCore/platform/graphics/chromium/LayerRendererChromium.cpp