[CKEditor Dev] #16869: Memory leak when creating / destroying inline instances
CKEditor
--------------------+-------------------------
Reporter: dvotion | Owner:
Type: Bug | Status: new
Priority: Normal | Component: General
Version: 4.6.1 | Keywords: memory leak
--------------------+-------------------------
When you dynamically create inline instances and then destroy an instance
with instanceName.destroy() the mutation observers aren't destroyed and
thus causing some serious memory leak and dom leakage.
On a page with multiple instances and a lot of user interaction this leak
quickly starts to grow big (multiple mb's per step) and causing the
ckeditor / browser to become really slow.
I've attached a screenshot of a heap snapshot comparison done in Chrome.
The steps I did were:
ActionSteps = create inline instance and then destroy it
1. do: ActionSteps
2. take Heapsnapshot
3. do: ActionSteps
4. take Heapsnapshot
5. do: ActionSteps
6. take Heapsnapshot
Then select heapsnapshot 3 and select from dropdown "Object allocated from
snapshot 1 and 2"
--
Ticket URL: <http://dev.ckeditor.com/ticket/16869>
CKEditor <http://ckeditor.com/>
The text editor for the Internet
CKEditor
Reporter: dvotion | Owner:
Type: Bug | Status: new
Component: General | Version: 4.6.1
Resolution: | Keywords: memory leak
----------------------+-------------------------
Changes (by dvotion):
* Attachment "memleak.png" added.
CKEditor
Reporter: dvotion | Owner:
Type: Bug | Status: confirmed
Priority: Normal | Milestone:
Component: General | Version: 4.0
Resolution: | Keywords:
----------------------+-----------------------
Changes (by j.swiderski):
* keywords: memory leak =>
* status: new => confirmed
* version: 4.6.1 => 4.0
Comment:
Other related issues: #16869, #12307, #11010, #13123.
--
Ticket URL: <http://dev.ckeditor.com/ticket/16869#comment:1>