Difference between revisions of "AppSuite:Memory leaks (UI)"
| Line 3: | Line 3: | ||
'''Intro''': Searching for memory leaks in the UI is not a pleasant task, but sadly necessary. | '''Intro''': Searching for memory leaks in the UI is not a pleasant task, but sadly necessary. | ||
| − | + | __TOC__ | |
| + | |||
| + | == Avoiding memory leaks == | ||
| + | |||
| + | '''resources:''' | ||
| + | *[https://www.ibm.com/developerworks/library/wa-memleak/ Memory leak patterns] | ||
== Issues == | == Issues == | ||
| Line 10: | Line 15: | ||
== Using Chrome == | == Using Chrome == | ||
Addy Osmani has written extensively on finding memory leaks with Chrome. His often-quoted article "[http://addyosmani.com/blog/taming-the-unicorn-easing-javascript-memory-profiling-in-devtools/ Taming the Unicorn]" explains how to use the Chrome DevTools for this purpose. | Addy Osmani has written extensively on finding memory leaks with Chrome. His often-quoted article "[http://addyosmani.com/blog/taming-the-unicorn-easing-javascript-memory-profiling-in-devtools/ Taming the Unicorn]" explains how to use the Chrome DevTools for this purpose. | ||
| + | |||
| + | '''additional resources:''' | ||
| + | * [https://developer.chrome.com/devtools/docs/heap-profiling-dom-leaks Uncovering DOM Leaks] | ||
| + | |||
Revision as of 05:48, 21 October 2014
Finding memory leaks in the UI
Intro: Searching for memory leaks in the UI is not a pleasant task, but sadly necessary.
Avoiding memory leaks
resources:
Issues
Different browsers offer different ways of tracing memory leaks. As of writing, the core team's favourite browser is Google Chrome.
Using Chrome
Addy Osmani has written extensively on finding memory leaks with Chrome. His often-quoted article "Taming the Unicorn" explains how to use the Chrome DevTools for this purpose.
additional resources: