Difference between revisions of "AppSuite:Memory leaks (UI)"

 
Line 1: Line 1:
<!-- !!! -->
+
The content on this page has moved to https://documentation.open-xchange.com/latest/ui/miscellaneous/memory-leaks.html
<!-- PLEASE APPLY CHANGES ONLY TO THE NEW TECHNICAL DOCUMENTATION: wd/frontend/web/documentation -->
 
<!-- !!! -->
 
  
<div class="title">Finding memory leaks in the UI</div>
+
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.
 
 
'''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 ==
 
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.
 
 
 
'''additional resources:'''
 
* [https://developer.chrome.com/devtools/docs/heap-profiling-dom-leaks Uncovering DOM Leaks]
 
 
 
 
 
 
 
 
 
[[Category: UI]]
 
[[Category: Developer]]
 
[[Category: Custom development]]
 
[[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.