Difference between revisions of "AppSuite:Memory leaks (UI)"
| Line 1: | Line 1: | ||
| + | <!-- !!! --> | ||
| + | <!-- PLEASE APPLY CHANGES ONLY TO THE NEW TECHNICAL DOCUMENTATION: wd/frontend/web/documentation --> | ||
| + | <!-- !!! --> | ||
| + | |||
<div class="title">Finding memory leaks in the UI</div> | <div class="title">Finding memory leaks in the UI</div> | ||
Revision as of 06:21, 11 February 2016
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: