[Webkit-unassigned] [Bug 96585] [chromium] NOT FOR REVIEW - gpu memmgr context lost prototype

[bugzilla-daemon at webkit.org]

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


Christopher Cameron <ccameron at chromium.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|cc-bugs at google.com,         |kbr at google.com,
                   |jamesr at chromium.org,        |nduca at chromium.org
                   |webkit.review.bot at gmail.com |




--- Comment #5 from Christopher Cameron <ccameron at chromium.org>  2012-09-12 18:02:17 PST ---
This works ONLY with threaded compositing (single-threaded hangs).  It also flashes checkerboards when switching to a tab that has had its context destroyed.

There are prints added that should add something like:
    <onControlledLostContext>
        In GPU process: GLContext::~GLContext (8 contexts exist)
    </onControlledLostContext>

The destruction of the renderer-side context is inside the re-creation logic.  This adds a separate function that does the renderer-side context destruction.

With just this patch, you won't see the "In GPU process" stuff -- you need  https://codereview.chromium.org/10913240 as well for that.

With just this patch, you'll also lose the context as soon as you change tabs.  With the non-WebKit patch, you'll be allowed a budget of 8 contexts.

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