From 6770b21e7d5f723057d63612a0d04f779f01888d Mon Sep 17 00:00:00 2001 From: Seojin Kim Date: Sun, 9 Sep 2012 19:26:39 +0900 Subject: [PATCH] [WK2] allow up to 64MB tile textures for 1 frame update [Title] [WK2] allow up to 64MB tile textures for 1 frame update [Issue #] N_SE-9731 [Problem] lockup when try to Reply the mail in gmail desktop site. [Cause] Too many layers are created in gmail desktop site, and moreover, contents forcely triggers relayout and paint infinitely. Sometimes, it creates so many graphics layers, and in turn, it creates too many tiles, and consequently causes out of shared memory space. [Solution] set texture memory limit up to 64MB [Developer] seojin.kim --- Source/WebKit2/WebProcess/WebPage/efl/LayerTreeHostEfl.cpp | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/Source/WebKit2/WebProcess/WebPage/efl/LayerTreeHostEfl.cpp b/Source/WebKit2/WebProcess/WebPage/efl/LayerTreeHostEfl.cpp index d7bccdd..6b372ba 100644 --- a/Source/WebKit2/WebProcess/WebPage/efl/LayerTreeHostEfl.cpp +++ b/Source/WebKit2/WebProcess/WebPage/efl/LayerTreeHostEfl.cpp @@ -632,6 +632,10 @@ PassOwnPtr LayerTreeHostEfl::beginContentUpdate(const } } + // Allow upto 4 atlases (= 64MB) + if (m_updateAtlases.size() >= 4) + return PassOwnPtr(); + static const int ScratchBufferDimension = 2000; m_updateAtlases.append(UpdateAtlas(ScratchBufferDimension, flags)); return m_updateAtlases.last().beginPaintingOnAvailableBuffer(handle, size, offset); -- 2.7.4