Opened 9 years ago

Last modified 5 years ago

#11010 confirmed Bug

Fix memory leaks caused by CKEDITOR.filter.instances storing nested editables' filters forever

Reported by: Piotrek Koszuliński Owned by:
Priority: Normal Milestone:
Component: UI : Widgets Version: 4.3
Keywords: Cc:


Every nested editable which has allowed content rules defined has its filter instance. These instances are stored in nested editable instances, which most likely are correctly garbage collected. But filter instances are also stored in CKEDITOR.filter.instances and they are kept there forever.

We could have filter.destroy() method removing instance from the instances hash and doing other cleanup if necessary. Then we could destroy filters when destroying widgets.

Change History (8)

comment:1 Changed 9 years ago by Jakub Ś

Status: newconfirmed

comment:2 Changed 9 years ago by Piotrek Koszuliński

Milestone: CKEditor 4.3.1CKEditor 4.3.2

comment:3 Changed 9 years ago by Piotrek Koszuliński

Milestone: CKEditor 4.3.2CKEditor 4.4

This requires new features to be implemented, so 4.4 is more reasonable.

comment:4 Changed 9 years ago by Piotrek Koszuliński

Milestone: CKEditor 4.4

Unfortunately, we'll not have enough time in 4.4 to handle this.

comment:5 Changed 7 years ago by Sead Memic

Will there be any progress soon on this bug?

comment:6 Changed 7 years ago by Jakub Ś

No one is currently working on this ticket right now, but thank you for team reminder.

I have talked with the team and we will consider giving this ticket a try in one of future releases (by future I mean no sooner than 4.5.8).

NOTE: You are welcome to leave another reminder one CKEditor 4.5.7 is out.

comment:7 Changed 6 years ago by Ehud Michelson

Any news about this defect?

comment:8 Changed 5 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