AppSuite:Memory leaks (UI): Difference between revisions
From Open-Xchange
(Created page with "'''Intro''': Searching for memory leaks in the UI is not a pleasant task, but sadly necessary. %TOC% == Issues == Different browsers offer different ways of tracing memory l...") |
No edit summary |
||
| Line 1: | Line 1: | ||
<div class="title">Finding memory leaks in the UI</div> | |||
'''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% | ||
== Issues == | == Issues == | ||
Revision as of 14:13, 20 October 2014
Finding memory leaks in the UI
Intro: Searching for memory leaks in the UI is not a pleasant task, but sadly necessary.
%toc%
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.