Opened 10 years ago
Last modified 7 years ago
#13123 confirmed Bug
Memory leak
| Reported by: | Owned by: | ||
|---|---|---|---|
| Priority: | Normal | Milestone: | |
| Component: | General | Version: | 4.0 |
| Keywords: | Cc: |
Description
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)
Change History (4)
Changed 10 years ago by
| Attachment: | ckeditor.html added |
|---|
comment:1 Changed 10 years ago by
| Keywords: | memory destroy removed |
|---|---|
| Status: | new → confirmed |
| Version: | 4.4.7 → 4.0 |
Note: See
TracTickets for help on using
tickets.
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.