Encountered error: WebGL context lost after resuming from sleep

[anjunhu]

Hello! I have encountered the following error after resuming my laptop from sleep. Please find relevant information below. I tried to reproduce this error but was not able to do so, please kindly disregard the report if it is ineligible as an issue. Sorry about the lack of a repro and further information, would appreciate if any developer could look into this. Thank you!

Encountered error: Defaulted to NaN results. Computing circuit values failed. (gl.getError() returned 0x9242 (CONTEXT_LOST_WEBGL) after texImage2D.)

Defaulted to NaN results. Computing circuit values failed.

URL https://algassert.com/quirk#circuit={%22cols%22:[[%22X%22],[%22Z^%C2%BD%22],[%22Z^%C2%BC%22]]}

BROWSER Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/86.0.4240.198 Safari/537.36 Netscape 5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/86.0.4240.198 Safari/537.36

RECOVERY DETAILS {"circuitDefinition": {"cols": [["X"], ["Z^½"], ["Z^¼"]]}}

ERROR OBJECT Error: gl.getError() returned 0x9242 (CONTEXT_LOST_WEBGL) after texImage2D.

ERROR LOCATION Error: gl.getError() returned 0x9242 (CONTEXT_LOST_WEBGL) after texImage2D. at e (https://algassert.com/quirk:363:575365) at i._textureAndFramebufferInitializer (https://algassert.com/quirk:363:568707) at $traceurRuntime.createClass.initializedValue.initializer (https://algassert.com/quirk:363:566872) at $traceurRuntime.createClass.initializedValue.initializedValue (https://algassert.com/quirk:363:559861) at initializedFramebuffer (https://algassert.com/quirk:363:567999) at e.renderToFunc (https://algassert.com/quirk:363:562382) at e.renderTo (https://algassert.com/quirk:363:555569) at e.renderToFunc (https://algassert.com/quirk:363:543442) at e.renderTo (https://algassert.com/quirk:363:555569) at e._renderToElseDealloc (https://algassert.com/quirk:363:555734)

PRE-DRAWN

POST-DRAWN

[Strilanc]

Did you have to refresh the page to get it working again, or it did it start working again after raising the error once?

These kinds of issues are surprisingly hard to reproduce, so I'm not sure if I will be able to fix it.