This screencast by Patrick Fitzgerald of BarelyFitz Designs discusses how he diagnosed and fixed a memory leak in a JavaScript library. It's a very simplified example, and the same techniques probably can't be used for more complex web applications, but it might shed some light on how these memory leaks occur.



 

Tags: Browsers, Internet Explorer, Debugging, Javascript

Level: any Date: April 02, 2009 Votes: 0 User: Dmytro Shteflyuk  Comments:
 
 

No Response(s) to this entry

Subscribe to comments with RSS.