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
--
Ticket URL: <http://dev.ckeditor.com/ticket/13123>
CKEditor <http://ckeditor.com/>
The text editor for the Internet
* status: new => confirmed
* keywords: memory,destroy =>
* version: 4.4.7 => 4.0
Comment:
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.
--
Ticket URL: <http://dev.ckeditor.com/ticket/13123#comment:1>
Comment (by j.swiderski):
Other tickets that concern memory leak: #11010, #7823, #5773.
--
Ticket URL: <http://dev.ckeditor.com/ticket/13123#comment:2>
Comment (by j.swiderski):
Other related issues: #16869, #12307, #11010, #13123.
--
Ticket URL: <http://dev.ckeditor.com/ticket/13123#comment:3>