How do you fix a ‘WebGL context lost’ event?
A webglcontextlost event usually means the browser's GPU process crashed, VRAM was exhausted, or the browser reached its limit of around 16 WebGL contexts per page, rather than a fault in your charting code. This is most commonly seen on integrated graphics adapters, such as older Intel HD GPUs, where a driver bug can cause the context to drop under load.
A few steps help reduce or resolve it. By default, SciChartSurface.create() uses a single shared WebGL context across all charts in your application, which avoids hitting the browser's per-page context limit. If you’re using SciChartSurface.createSingle() for a large number of charts instead, switching to create() is often the fix. Also make sure your GPU drivers are up to date, since several context loss issues have been traced to driver bugs on specific hardware. SciChart.js includes logic to properly recover from a lost WebGL context where possible, so keeping your SciChart.js version current is worthwhile too.