Memory Leaks about angular-gm

[dylanfprice]

Hi Matthiue,

Thanks for bringing this up. For anyone else who's interested, here's some more info: http://stackoverflow.com/questions/10485582/what-is-the-proper-way-to-destroy-a-map-instance

I can try something similar to your idea and let you know how it goes.

[MatthieuBarthel]

Hi dylanfprice,

Thanks for your reply, I worked on it and came up with a proof of concept :
http://plnkr.co/edit/zxhJgOQEhPxPAX9AUCGs?p=preview

The rescue/reuse technique gives good results, tell me what you think and if I can help you for something.

[dylanfprice]

Cool thanks for doing that. I will have some time to add this in at the end of this week.

[MatthieuBarthel]

That's awesome thanks a lot, I'm looking forward for your release 👍

[dylanfprice]

I got your basic idea working and put it in a separate branch: https://github.com/dylanfprice/angular-gm/tree/memory-leak-fix

It's not quite ready yet because I need to deal with a few issues like refreshing stale markers on the map.

I went ahead and put a build of the memory-leak-fix branch up: http://dylanfprice.github.io/angular-gm/angular-gm-0.1.0-memory-leak-fix.js. Let me know if that solves your memory leak and I'll fix those remaining issues!

[MatthieuBarthel]

Your are awesome, thank you !

I did an automated memory test, going through 300 views during 5 minutes, each view got a map, and here are the results:

• master branch : the memory grows up to 280MB
• memory-leak-fix branch: the memory never go upper then 35MB

Do not hesitate if I can do anything to help you.