Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Too many active WebGL contexts. Oldest context will be lost

See original GitHub issue

It looks like purging a scattergl graph does not destroy the webgl context. I have a page with 4 scattergl plots on it that are redrawn (purge and newPlot) when zooming in on data (as it downloads higher resolution data). Once the graphs are redrawn a couple of times, you start getting the WebGL warning messages. Was wondering if the GL context wasn’t being “removed completely” on purge (related issues https://github.com/pixijs/pixi.js/issues/2233#issuecomment-181650433)?

Hack of an example https://codepen.io/bytesnz/pen/XBaoee

Issue Analytics

State:
Created 5 years ago
Comments:9 (5 by maintainers)

Top GitHub Comments

1reaction

bytesnzcommented, Jul 31, 2018

I was using purge/newPlot to avoid other issues we were getting. What exactly they were, I will have to test again using just react and let you know. Will close and approach browsers.

1reaction

alexcjohnsoncommented, Jul 31, 2018

@bytesnz this does seem like a browser issue, but I wonder if you’ve tried using Plotly.react instead of purge+newPlot? That should give the same result but in principle it reuses resources like webGL contexts.