id	summary	reporter	owner	description	type	status	priority	milestone	component	version	resolution	keywords	cc
5317	Create tool to improve detection of non released memory	Alfonso Martínez de Lizarrondo		"Follow up of #4555

It's not the typical ""memory leak"" problem present in the browsers, but it's easy to store data in a way that it isn't released after one instance is destroyed in an AJAX way, and that means more and more memory use, so it's in the end a memory leak.

In the previous bug we have cleaned up the main codeline, but there are other parts that will have to be reviewed and instead of trying to dig into every plugin we must try to find an automated way that help us diagnose where are the problems."	Task	pending	Normal		QA	3.0