Opened 8 years ago
Last modified 8 years ago
#16869 confirmed Bug
Memory leak when creating / destroying inline instances
Reported by: | dvotion | Owned by: | |
---|---|---|---|
Priority: | Normal | Milestone: | |
Component: | General | Version: | 4.0 |
Keywords: | Cc: |
Description
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
- do: ActionSteps
- take Heapsnapshot
- do: ActionSteps
- take Heapsnapshot
- do: ActionSteps
- take Heapsnapshot
Then select heapsnapshot 3 and select from dropdown "Object allocated from snapshot 1 and 2"
Attachments (1)
Change History (2)
Changed 8 years ago by
Attachment: | memleak.png added |
---|
comment:1 Changed 8 years ago by
Keywords: | memory leak removed |
---|---|
Status: | new → confirmed |
Version: | 4.6.1 → 4.0 |
Other related issues: #16869, #12307, #11010, #13123.