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
 
(4 intermediate revisions by 2 users not shown)
Line 1: Line 1:
'''Intro''': Searching for memory leaks in the UI is not a pleasant task, but sadly necessary.
The content on this page has moved to https://documentation.open-xchange.com/latest/ui/miscellaneous/memory-leaks.html


%TOC%
Note: Open-Xchange is in the process of migrating all its technical documentation to a new and improved documentation system (documentation.open-xchange.com). Please note as the migration takes place more information will be available on the new system and less on this system. Thank you for your understanding during this period of transition.
 
== 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 "[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.
 
 
 
[[Category: UI]]
[[Category: Developer]]
[[Category: AppSuite]]

Latest revision as of 10:09, 22 May 2017

The content on this page has moved to https://documentation.open-xchange.com/latest/ui/miscellaneous/memory-leaks.html

Note: Open-Xchange is in the process of migrating all its technical documentation to a new and improved documentation system (documentation.open-xchange.com). Please note as the migration takes place more information will be available on the new system and less on this system. Thank you for your understanding during this period of transition.