Opened 9 years ago

Last modified 6 years ago

#13123 confirmed Bug

Memory leak

Reported by: dumkac@… Owned by:
Priority: Normal Milestone:
Component: General Version: 4.0
Keywords: Cc:


Memory is not released after destroying ckeditor instance.

How to reproduce: -open attached file in chrome -start record heap allocation (Chrome/DeveloperTools/Profiles/RecordHeapAllocations) -click on "add" -click on "remove" -stop record heap allocation -check memory leak

Attachments (1)

ckeditor.html (3.0 KB) - added by dumkac@… 9 years ago.

Download all attachments as: .zip

Change History (4)

Changed 9 years ago by dumkac@…

Attachment: ckeditor.html added

comment:1 Changed 9 years ago by Jakub Ś

Keywords: memory destroy removed
Status: newconfirmed

Minor memory leaks are a known issue, but due to the size of CKEditor and level of its complexness, number of supported browsers and high level of code branching caused by the browsers, the cost of fixing them is high. We focus therefore on significant memory leaks only. For instance, few months ago a problem with CKEDITOR.filter instances was fixed because filter instances are pretty costly for the memory. If you spotted any other memory leak of this size, please let us know.

comment:2 Changed 9 years ago by Jakub Ś

Other tickets that concern memory leak: #11010, #7823, #5773.

comment:3 Changed 6 years ago by Jakub Ś

Other related issues: #16869, #12307, #11010, #13123.

Note: See TracTickets for help on using tickets.
© 2003 – 2022, CKSource sp. z o.o. sp.k. All rights reserved. | Terms of use | Privacy policy