AppSuite:Memory leaks (UI) - Revision history

Khgras at 10:09, 22 May 2017

2017-05-22T10:09:25Z

← Older revision		Revision as of 10:09, 22 May 2017
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]]~~

Frank.paczynski at 06:21, 11 February 2016

2016-02-11T06:21:05Z

← Older revision		Revision as of 06:21, 11 February 2016
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>

Frank.paczynski at 05:48, 21 October 2014

2014-10-21T05:48:48Z

← Older revision		Revision as of 05:48, 21 October 2014
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%~~		__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]

Tierlieb at 14:15, 20 October 2014

2014-10-20T14:15:03Z

← Older revision		Revision as of 14:15, 20 October 2014
Line 15:		Line 15:
	[[Category: UI]]		[[Category: UI]]
	[[Category: Developer]]		[[Category: Developer]]
			[[Category: Custom development]]
	[[Category: AppSuite]]		[[Category: AppSuite]]

Tierlieb at 14:13, 20 October 2014

2014-10-20T14:13:27Z

← Older revision		Revision as of 14:13, 20 October 2014
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~~%		%toc%

	== Issues ==		== Issues ==

Tierlieb: 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..."

2014-10-20T14:11:36Z

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..."

New page

'''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 "[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]]