Leaflet leaks memory on iOS 7

[mourner]

iOS7 Safari crashes too fast on Leaflet 0.6 (e.g. clustering 3000 markers), while it's not on 0.5.1 (even with 10000).

Original issue: Leaflet/Leaflet.markercluster#254
Commit that introduces the leak: 8e65fe7
Related pull request: #1514

[mourner]

What's very funny is that this commit introduces memory leak in iOS7, but not iOS6. So we should clearly also report that to iOS 7 devs.

[klimashkin]

Faced with a similar problem 3 weeks ago, only in chrome> 28, but with my clustering system.
In half of the cases chrome was falling (completely) when I clustered more than 2,000 markers.
The problem was in "aggressive optimization" for creating of hundreds of new clusters objects within loop if they first created with "blank" properties. Resolved when creating objects already filled immediately.
But there v8..

[mourner]

@klimashkin could you give an example of this?

[danzel]

sent PR #2149 to fix this, at least for the 10k marker cluster use case.

[fab1an]

I still have the problem that my leaflet-page crashes on iOS7 / iPhone 4s. I don't use markers at all, just a lot of svg-vectors.

[fab1an]

Comment from here http://stackoverflow.com/questions/3971218/techniques-for-profiling-memory-in-safari-desktop-and-ios

"One thing we found when developing for the iPad in particular was that it was very prone to crashing due to memory issues, particularly in image heavy applications like ours. One thing we learned was that just removing a DOM element does not mean that element will be garbage collected by the browser. We found that setting the image src (or background-image, if it was a div) to an empty string before removing it from the DOM helped immensely."

[mourner]

According to various reports, the memory issue is fixed in iOS 7.1, which is now in beta. Leaflet can't do much about the current situation because it's a pretty nasty OS bug. :( Re the comment — we already do "clean up" of tile images.