quoted from https://github.com/mapbox/mapbox-gl-js/issues/4695#issuecomment-305221298
I've been digging deeper into this, and it seems like there is a memory leak in Safari on both mobile and desktop for mapbox-gl-js.
All mobile debugging have been done with the basic mapbox example https://www.mapbox.com/mapbox-gl-js/examples/
on an iPad Pro 6,3 (2 GB ram) running iOS 10.3.1. Desktop debugging was done on OS X Safari 10.1.
The error message is "A problem occurred with this webpage so it was reloaded" adding it so people can find this bug if looking for it
There does look to be a WebGL-related leak here. We'd have to check whether the page is entraining the data.
@smfr, we're unable to isolate the issue to a single aspect of mapbox-gl-js. In addition, the same benchmarking tests causes another popular web-gl based map library, Tangram [https://github.com/tangrams/tangram] to crash on iOS devices as well. See https://github.com/mapbox/mapbox-gl-js/issues/4695#issuecomment-323087798 for details.
Let me know if you'd like an isolated test case for this issue.
(In reply to Kristian F from comment #4)
> @smfr, we're unable to isolate the issue to a single aspect of mapbox-gl-js.
> In addition, the same benchmarking tests causes another popular web-gl based
> map library, Tangram [https://github.com/tangrams/tangram] to crash on iOS
> devices as well. See
> for details.
> Let me know if you'd like an isolated test case for this issue.
The answer to “would you like an isolated reproducible test case?” is almost always *yes* :)
Thanks for your help tracking this down!
Np, let me know if there is anything else I can do to help resolve this!
You'll find a test example here: https://kristfal.github.io/mapbox-memory-test/
To reproduce a OOM crash:
1) Open the web page above on an iPad. They make the best test case due to larger screen size. I'd recommend using an iPad A1475 or another model with 1 GB RAM for consistent and quick results
2) Press Start in the top left corner and the map will start animating through a predefined path and load map tiles as it animates
3) Memory usage will continue to increase until the browser tab eventually crashes and reloads with the 'A problem occurred..' message
For iPads with 2GB memory, this happens when the com.apple.Webkit process has consumed between 750 and 850 MB of "Real memory". For iPads with 1GB memory, this happens at around 400 - 500 MB.
Drop me a line if you have any questions or if you're unable to reproduce the crash.
Any updates on this? The memory leak and Safari crashing is release blocker for our customer and we would like to know what is the status of this bug? As stated earlier in this thread the crashing happens both in desktop and mobile Safari. We’ve also came across this memory leak when mapbox-gl-js map was removed and re-initialised. Currently we’re working on workarounds by removing and re-initialising the map from time to time but this causes map to blink and it is not a viable solution on a long run.
(In reply to Kristian F from comment #6)
> Np, let me know if there is anything else I can do to help resolve this!
> You'll find a test example here:
This test doesn't work:
[Error] Failed to load resource: the server responded with a status of 401 (Unauthorized) (streets-v9, line 0)
Any update on this? +1
I'm having trouble reproducing this with the map box example site on an iPad Pro 6,3 (as originally reported) running iOS 12. If you are still seeing this, please post your SW/HW configuration.
Kristian's test seems to be relying on an expired API key.
Kristian has fixed the test