id	summary	reporter	owner	description	type	status	priority	milestone	component	version	resolution	keywords	cc
12261	Filter has to be destroyed and removed from CKEDITOR.filter.instances on editor destroy	Piotrek Koszuliński	Artur Delura	"This issue is related to #11010 (it's a sub case of it).

When filter is created it's registered in CKEDITOR.filter.instances. Unfortunately, we haven't got time to implement any mechanism cleaning this on editor destroy. Therefore, when system destroys and initialises editors many time, the pile of filters grows and each filter consumes pretty a lot of memory.

The solution should be simple. From my tests it seems that this will be enough:

* Implement filter.destroy() that will for safety delete the private object (this._) which keeps a lot of stuff and will remove editor from CKEDITOR.filter.instances.
* Call editor.filter.destroy() and delete editor.filter and editor.activeFilter on editor#destroy

We can also track some other big objects that are retained after editor destroy and try deleting references we know off. Sometimes it won't help, but some times it may.

Based on http://ckeditor.com/forums/CKEditor/CKEditor-multiple-instance-memory-leak"	Bug	closed	Normal	CKEditor 4.4.5	General	4.3	fixed