[Webkit-unassigned] [Bug 105732] New: [chromium] DrawingBuffer initialization loop breaks if completely out of memory

[bugzilla-daemon at webkit.org]

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

           Summary: [chromium] DrawingBuffer initialization loop breaks if
                    completely out of memory
           Product: WebKit
           Version: 528+ (Nightly build)
          Platform: All
        OS/Version: All
            Status: NEW
          Severity: Normal
          Priority: P2
         Component: WebGL
        AssignedTo: webkit-unassigned at lists.webkit.org
        ReportedBy: kbr at google.com
                CC: zmo at google.com, gman at google.com, bajones at chromium.org


Brandon Jones discovered while debugging Issue 104733 and Issue 105367 that if s_currentResourceUsePixels is at the maximum, DrawingBuffer initialization will silently fail, and the WebGL context will silently display nothing. This behavior needs to be improved. At a minimum, context creation should probably report failure.

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