Hi! Thanks for reporting this! First of all - devtools are open initially on purpose, exactly to catch errors like this (might be somewhat inconvenient, but that's temporary measures during development).
Now, as for the error itself - this is something new, I haven't seen such an error before. Quick research shows that it may happen when WebGL context is lost:
https://developer.mozilla.org/en-US/docs/Web/API/WebGLRenderingContext/isContext...
This is a technical article, you don't have to read it, I'm just putting it here as a reference for the future. What it says, importantly, is that such an error can occur when:
- Two or more pages are using the GPU, but together place too high a demand on the GPU, so the browser tells the two contexts that they've lost the connection, then selects one of the two to restore access for.
- The user's computer has multiple graphics processors (such as a laptop with both mobile and desktop class GPUs, the former used primarily when on battery power), and the user or system decides to switch GPUs. In this case, all contexts are lost, then restored after switching GPUs.
- Another page running in the user's browser performs an operation using the GPU that takes too long, causing the browser to decide to reset the GPU in order to break the stall. This would cause every WebGL context to be lost throughout the entire browser.
- The user updates their graphics driver on an operating system that allows graphics drivers to be updated without restarting the system.
Does any of these statements sound like something that could've happened in your situation?