Changeset 117485 in webkit
- Timestamp:
- May 17, 2012 1:04:08 PM (12 years ago)
- Location:
- trunk/Source/WebCore
- Files:
-
- 2 edited
Legend:
- Unmodified
- Added
- Removed
-
trunk/Source/WebCore/ChangeLog
r117484 r117485 1 2012-05-17 Michal Mocny <mmocny@google.com> 2 3 [chromium] Limiting render surface texture manager memory to 0 when contentsMemoryUseBytes is large. 4 https://bugs.webkit.org/show_bug.cgi?id=86764 5 6 Reviewed by Adrienne Walker. 7 8 * platform/graphics/chromium/LayerRendererChromium.cpp: 9 (WebCore::LayerRendererChromium::beginDrawingFrame): 10 1 11 2012-05-17 Dan Bernstein <mitz@apple.com> 2 12 -
trunk/Source/WebCore/platform/graphics/chromium/LayerRendererChromium.cpp
r116779 r117485 417 417 size_t contentsMemoryUseBytes = m_contentsTextureAllocator->currentMemoryUseBytes(); 418 418 size_t maxLimit = TextureManager::highLimitBytes(viewportSize()); 419 m_renderSurfaceTextureManager->setMaxMemoryLimitBytes(maxLimit - contentsMemoryUseBytes); 419 size_t newLimit = (maxLimit > contentsMemoryUseBytes) ? maxLimit - contentsMemoryUseBytes : 0; 420 m_renderSurfaceTextureManager->setMaxMemoryLimitBytes(newLimit); 420 421 421 422 if (viewportSize().isEmpty())
Note: See TracChangeset
for help on using the changeset viewer.