A Step-by-step guide to finding memory leaks
Posted by Dion Almaer about a year ago on heap memory performance profile
Web developers have lived much of their lives with a magic garbage collector known as going from page to page. The user experience of tearing down and loading a new page may be suboptimal, but at least we don’t have long running applications that require us to make sure that we don’t leak memory!
That all changed with Ajax. Well, kinda. For every true app like Gmail, we gained a thousand web sites with a sprinkle of jQuery on top.
But now. Nooooow is the time of the rich client JavaScript apps!
So, it is time to get serious.
Tony Gentilcore, Google Web performance guru extraordinaire, pondered why developers didn’t seem to be talking about the heap profiler.
He goes on to walk through finding a memory leak in facebook.com.
It is awesome to see. It makes you boot up your web app right away and watch the memory.