[Webkit-unassigned] [Bug 218305] New: WebGL context remains in memory after calling loseContext()

[bugzilla-daemon at webkit.org]

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

            Bug ID: 218305
           Summary: WebGL context remains in memory after calling
                    loseContext()
           Product: WebKit
           Version: Safari 14
          Hardware: Unspecified
                OS: Unspecified
            Status: NEW
          Severity: Normal
          Priority: P2
         Component: WebGL
          Assignee: webkit-unassigned at lists.webkit.org
          Reporter: philipbell at google.com
                CC: dino at apple.com

To reproduce: 
Create over 16 WebGL contexts and call loseContext on each.
On the 17th call two errors will be thrown: 
> ‘There are too many active WebGL contexts on this page, the oldest context will be lost.’
> ‘WebGL: INVALID_OPERATION: loseContext: context already lost’
It's expected that these contexts would not remain in memory.

Code snippet:
for (let i = 0; i < 17; i++) {
  const canvas = document.createElement('canvas');
  const gl = canvas.getContext('webgl');  
  const extension = gl.getExtension('WEBGL_lose_context')
  extension.loseContext();
}

Example CodePen of dynamically losing & restoring contexts.
https://codepen.io/philipbell/pen/RwRQGmo

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.webkit.org/pipermail/webkit-unassigned/attachments/20201028/c406eaba/attachment.htm>