Your SlideShare is downloading. ×
JavaScript Leaks
Upcoming SlideShare
Loading in...5

Thanks for flagging this SlideShare!

Oops! An error has occurred.

Saving this for later? Get the SlideShare app to save on your phone or tablet. Read anywhere, anytime – even offline.
Text the download link to your phone
Standard text messaging rates apply

JavaScript Leaks


Published on

Defining and understanding how memory leaks happen in JavaScript. …

Defining and understanding how memory leaks happen in JavaScript.

Published in: Technology
  • Be the first to comment

No Downloads
Total Views
On Slideshare
From Embeds
Number of Embeds
Embeds 0
No embeds

Report content
Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

No notes for slide


  • 1. Javascript memory leaks Christian Boisjoli, SilenceIT
  • 2. Javascript Memory Leaks
    • What a memory leak is
    • How memory leaks occur in Javascript
    • How to avoid memory leaks
    • Effects of memory leaks
    • How much browsers are affected by leaks
    • Detection of leaks
  • 3. What a memory leak is
    • In its simplest form, a memory leak occurs when a program does not release memory it allocated
    • Misuse of global scope
    • Complex objects not being automatically freed by programming language
    • Analogy: renting a movie, not returning it until the time limit is about to end
  • 4. How memory leaks in Javascript
    • Misuse or accidental use of global scope, e.g. some anonymous functions, undeclared variables
    • Closures with DOM elements / event handlers
    • Event handlers (mostly with IE)
    • Circular references
    • Technically, use of objects, not including AJAX
  • 5. How to avoid memory leaks
    • Use the global scope only when appropriate
    • Always declare variables in functions when you use them
    • Use a collector to keep references to elements with event handlers
    • Avoid closures with event handlers and functions that attach event handlers OR use a global event handler that delegates to listeners
    • Avoid dealing with DOM elements in closures OR remember to null them afterwards
    • Detach circular references when you are done with them (Try to avoid them altogether)
  • 6. Effect leaks have
    • Leaks will slow down the browser as the process consumes more memory
    • Leaks will slow down the operating system and other processes as the bigger process is given more room
    • Some browsers handle leaks better than others (e.g. IE8 uses whole separate processes per tab)
    • Often will usually carry the “load” until closed, so this does not only apply to web applications
  • 7. Incoming graphs
    • Memory usage deltas are important, not sheer quantities
    • Firefox 3's stats may be inaccurate, particularly because it never completed the array test
    • Some tests are not included because they affected only Internet Explorer, and version 8 (somewhat) fixed these
    • A few events were accidentally omitted
  • 8.  
  • 9.  
  • 10.  
  • 11.  
  • 12.  
  • 13.  
  • 14.  
  • 15. Detection of memory leaks
    • Internet Explorer JavaScript Memory Leak Detector (v2):
    • Mozilla: Performance: Tools
    • JavaScript Memory Validator
  • 16. More information
    • Memory leak patterns in JavaScript
    • Understanding and Solving Internet Explorer Leak Patterns
  • 17. Questions?