[Webkit-unassigned] [Bug 66981] New: [Chromium] Possible leak of LayerRendererChromium

[bugzilla-daemon at webkit.org]

https://bugs.webkit.org/show_bug.cgi?id=66981

           Summary: [Chromium] Possible leak of LayerRendererChromium
           Product: WebKit
           Version: 528+ (Nightly build)
          Platform: Unspecified
        OS/Version: Unspecified
            Status: NEW
          Severity: Normal
          Priority: P2
         Component: Layout and Rendering
        AssignedTo: webkit-unassigned at lists.webkit.org
        ReportedBy: satish at chromium.org
                CC: jamesr at chromium.org


Opening and closing multiple tabs in the same process with hardware acceleration enabled seems to be causing an unbounded increase in the process's memory usage. It looks like LayerRendererChromium objects are staying alive forever after the page is closed, possibly due to a circular reference.

Steps to reproduce:
1. Run chrome with --force-compositing-mode argument
2. open chrome:memory
3. open build.webkit.org in 2 tabs, check that they appear under the same process in chrome:memory
4. close one of them, then open the same site again
5. repeat (4) multiple times

Refresh chrome:memory and the GPU process should show a much higher memory usage than in (3)

Also tried by forcing a GC and saw no drop in memory used.

-- 
Configure bugmail: https://bugs.webkit.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.