Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Remove the window.editor from memory leaks tests. #1814

Assignees
Labels
type:task This issue reports a chore (non-production change) and other types of "todos".
Milestone

Comments

@jodator
Copy link
Contributor

jodator commented Jun 14, 2019

The CKEditor5 causes some memory leaks and the editor should not be automatically attached to the inspector for memory leak tests.

@oleq
Copy link
Member

oleq commented Jun 17, 2019

Somehow related: Could you please take a look at the CKEditorInspector.destroy() API implemented in ckeditor/ckeditor5-inspector#46?

oleq added a commit to ckeditor/ckeditor5-editor-inline that referenced this issue Jun 18, 2019
Tests: Prevented `CKEditorInspector` auto–attachment in the memory consumption manual test. Closes ckeditor/ckeditor5#1814.
oleq added a commit to ckeditor/ckeditor5-editor-classic that referenced this issue Jun 18, 2019
Tests: Prevented `CKEditorInspector` auto–attachment in the memory consumption manual test. Closes ckeditor/ckeditor5#1814.
oleq added a commit to ckeditor/ckeditor5-editor-balloon that referenced this issue Jun 18, 2019
Tests: Prevented `CKEditorInspector` auto–attachment in the memory consumption manual test. Closes ckeditor/ckeditor5#1814.
oleq added a commit to ckeditor/ckeditor5-editor-decoupled that referenced this issue Jun 18, 2019
Tests: Prevented `CKEditorInspector` auto–attachment in the memory consumption manual test. Closes ckeditor/ckeditor5#1814.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment