Hi all,
I am currently working on a web app wich allow user to create emails. Each time I create an email I create a backbone view with a new CKEditor instance.
After sent many emails, I had a look on the profiler of chrome to see if there is some memory leak.
I found some references to CKEDITOR.filter. And each time I create a new view a new filter instance is created in CKEDITOR.filter.instances.
After looking on the Ckeditor website I found : http://dev.ckeditor.com/ticket/11010
Is there a solution to remove correctly a ckeditor instance without memory leak ?
Currently I am using .destroy() but it doesn't seems enough. I don't know how to deal with these filter instances.
I am using the latest version of CKEditor
Thanks for any help
Regards
I can see this. During editor
I can see this. During editor lifetime only one CKEDITOR.filter exists (unless you use widgets with nested editables), but as soon as you start destroying and initialising editors again the number grows. That's because filter is not garbage collected when editor is being destroyed.
This issue has nothing to do with http://dev.ckeditor.com/ticket/11010. The one you encounter seems to be more general - related to filter or editor itself. I couldn't find what's keeping the instance yet and I anticipate very time consuming debugging, so if you have any ideas, please let us know.
Piotrek (Reinmar) Koszuliński
CKEditor JavaScript Developer
--
CKSource - http://cksource.com
--
Follow CKEditor on: Twitter | Facebook | Google+
This issue has nothing to do
Turns out I wasn't right. It's caused by the same mechanism as #11010, although it indeed happens on more general (editor instance) layer. I reported http://dev.ckeditor.com/ticket/12261 with more details.
Piotrek (Reinmar) Koszuliński
CKEditor JavaScript Developer
--
CKSource - http://cksource.com
--
Follow CKEditor on: Twitter | Facebook | Google+