[Webkit-unassigned] [Bug 91130] New: [chromium] Fix initialization race to determine the initial memory limit

[bugzilla-daemon at webkit.org]

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

           Summary: [chromium] Fix initialization race to determine the
                    initial memory limit
           Product: WebKit
           Version: 528+ (Nightly build)
          Platform: Unspecified
        OS/Version: Unspecified
            Status: NEW
          Severity: Normal
          Priority: P2
         Component: WebCore Misc.
        AssignedTo: webkit-unassigned at lists.webkit.org
        ReportedBy: epenner at chromium.org


In LayerRendererChromium, we set the memory limit via a callback:

    if (m_capabilities.usingGpuMemoryManager)
        m_context->setMemoryAllocationChangedCallbackCHROMIUM(this);
    else
        m_context->m_client->setMemoryAllocationLimitBytes(some_default);

However, this leaves us with the question of what to do before we get the callback should we:
- Wait for the callback before rendering anything?
- Keep using a default a like we do currently?
- Use a synchronous call to get the limit rather than a callback? It could decide whether to block etc. or just return the default itself?


Another issue is that it is not effective to set the default in this location in LayerRendererChromium. Currently we also need
to set it in the CCLayerTreeHostImpl constructor, so our initialization in LayerRendererChromium is not early enough.

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