Open ivaylopivanov opened 9 years ago
well there is no destroy
for google map, the only way they recommend to destroy
a map is to set map
to null to all objects on it, and that is done after all listeners are removed.
How are you seeing this memory leak and when? Do you have an example repo where it could be tested and checked as well as used to try to fix that issue?
I'm using chrome heap snapshots. Unfortunately, for the moment I don't have time to put it on a public repository, since the one that I'm working on is a private one. The workaround for me was to put it as modal in application and only show/hide it
I'm not sure is this a known issue for you guys, but obviously removing only the listeners is not good enough for gc. Any ideas ?