I just came across this article by Douglas Crockford earlier tonight regarding JavaScript memory leaks especially in Internet Explorer. The article does a fine job of explaining what it is and how to patch the memory leakage issues.
What better way to learn the concept/technique than actually applying it. I set out to rid the known memory leakages that exist on my pet project, World Cup Pickr. Even though it’s still not 100% free from memory leaks, it’s definitely better than before. Until then, I will continue tweaking and patching leaks where I see fit.
Also, in order to refresh my memory of the Yahoo AJAX Maps API, I integrated and added Yahoo Maps right next to the existing Google Maps for my AJAX pet project, AJAX Mashup Traffic Check. I finally got them both to sync up and display the same set of icons accordingly. As one map is dragged around, the other map pans accordingly to match by latitude/longitude.
In the process of integration, I updated Google Maps API to version 2. They have changed things around quite a bit, renamed a good number of functions. Originally, with version 1, Google used to list geo-points by longitude first and then latitude. It’s a bit awkward if you ask me. Fast forward to version 2, Google has finally reversed it so now it is matching with how Yahoo! has been doing things from the start.
I also upgraded the Yahoo! Local Search REST Web Service from version 1 to version 2. I’m not exactly sure what has changed since version 1, but it seems to be working the same way like before…
Warning – My AJAX web application is not very optimized and it acts as my little sandbox for playing around with the maps API’s. Memory leaks are highly likely to occur, especially of its AJAXy nature. Anyhow, do check it out and let me know if you have encountered any bugs. =)
1
- Allison - 819 days ago
coolio :)
next thing on your to-do list: teach me how to do all this ;)
I love you!