Open sfahnens opened 4 years ago
Same problem within an Angular Web App. Is it possible please to add an automatic ext.restoreContext() in your next version ?
I got the same issue. Is there a solution to this problem?
My solution is to use Leaflet, Google Maps or AWS Location Services.
Any updates?
Also running into this issue - would be really interested in hearing from anyone who's been able to handle context loss in mapbox-gl
any updates?
I got the same issue. Is there a solution to this problem?
Hi, any update?
Hi, any update?
Check if you are using another package that uses WebGL
it's 2024 now, any updates?
mapbox-gl-js version: 1.9.1 / latest release (or whatever the examples page uses.)
browsers:
Steps to Trigger Behavior / Link to Demonstration
Expected Behavior
Map view goes blank on .loseContext() and comes back on .restoreContext().
Actual Behavior
Map view goes blank but does not come back. Instead many WebGL errors appear on the console:
WebGL: INVALID_OPERATION: bindBuffer: object does not belong to this context value.js:403 WebGL: INVALID_OPERATION: bindBuffer: object does not belong to this context value.js:416 WebGL: INVALID_OPERATION: bindTexture: object does not belong to this context line_atlas.js:200 WebGL: INVALID_OPERATION: bindTexture: object does not belong to this context texture.js:92
Notes
I discovered the problem while experimenting with a custom layer. Our stuff came right back after handling the appropriate events ("webglcontextlost" and "webglcontextrestored"). Otherwise, similar bindBuffer errors occur. After some panning and zooming around it looks like the map (line and symbols layers) works everywhere, but in area/zoom that were active when lose/restore happened.
For the example map only the symbol layers seems to work elsewhere?!
I'm not really sure if this is a real problem, or occurs only with the extension. However I'm not aware of another possibility to trigger context loss for debugging purposes, so it would be nice if this works :)