Check the editor for memory leaks after interacting with it

[jodator]

During debugging/fixing the memory leaks of an editor that is created/destroyed (#1341) I've narrowed down my scope to only instantiating and destroying the editor. But reviewing some parts of code I've discovered that some features like FocusCycler, MutationObservers adds listeners to DOM nodes and they can (AFAIR) add them during the editor lifecycle.

In other words we still need to check the editor for any memory leaks that may occur while interacting with the editor. This will include:

• typing
• using undo/redo
• moving the focus over the toolbar
• selecting widgets (table, image, media, ...) and interacting with widget toolbars
• pasting
• pasting images
• embedding media
• selecting text, elements, moving selection, etc

If we found out any memory leaks (and I strongly believe that we still may) we should introduce another set of automated tests if possible.

[CKEditorBot]

There has been no activity on this issue for the past year. We've marked it as stale and will close it in 30 days. We understand it may be relevant, so if you're interested in the solution, leave a comment or reaction under this issue.

[CKEditorBot]

We've closed your issue due to inactivity over the last year. We understand that the issue may still be relevant. If so, feel free to open a new one (and link this issue to it).