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.

Sign up for GitHub

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

Jump to bottom

Check for potential memory leaks #589

Closed
jswiderski opened this issue Jun 30, 2017 · 1 comment
Closed

Check for potential memory leaks #589

jswiderski opened this issue Jun 30, 2017 · 1 comment
Assignees
@engineering-this
Labels
status:confirmed An issue confirmed by the development team. support:1 An issue reported by a commercially licensed client. target:minor Any docs related issue that can be merged into a master or major branch. type:bug A bug.
Milestone
4.11.4

Comments

@jswiderski
Copy link
Contributor

jswiderski commented Jun 30, 2017 •
edited by f1ames
Loading

Are you reporting a feature or a bug?

Bug

Check if the issue is already reported

Provide detailed reproduction steps (if any)

  1. Open AJAX sample in Chrome with dev tools enabled and set to memory tab
  2. Create editor and take a memory snapshot.
  3. Destroy editor and take memory snapshot
  4. Repeat steps 2 & 3 few times

Expected result

Everything or almost everything is released.

NOTE: From what I remember getData should work after destroying the editor and should return actual editor data (I don't remember what was the exact reason behind it though).

Actual result

There are a lot of DOM objects being left behind.

  • Browser: Any
  • OS: Any
  • CKEditor version: at least from 3.0
  • Installed CKEditor plugins: N/A
@f1ames f1ames added status:confirmed An issue confirmed by the development team. type:bug A bug. labels Dec 11, 2017
@mlewand mlewand added support An issue reported by a commercially licensed client. target:minor Any docs related issue that can be merged into a master or major branch. labels Nov 14, 2018
@mlewand mlewand added this to the Backlog milestone Nov 14, 2018
@mlewand mlewand changed the title [Microsoft] Check for potential memory leaks Check for potential memory leaks Nov 14, 2018
@lslowikowska lslowikowska added support:3 An issue reported by a commercially licensed client. and removed support An issue reported by a commercially licensed client. labels Jan 9, 2019
@engineering-this engineering-this self-assigned this Mar 12, 2019
This was referenced Mar 19, 2019
Closed
Merged
@f1ames f1ames modified the milestones: Backlog, 4.11.4 Mar 22, 2019
@f1ames f1ames mentioned this issue Mar 25, 2019
Open
@f1ames
Copy link
Contributor

f1ames commented Mar 26, 2019

Closed in 20caee9.

@f1ames f1ames closed this as completed Mar 26, 2019
@engineering-this engineering-this mentioned this issue Jul 23, 2019
Merged
2 tasks
@lslowikowska lslowikowska added support:1 An issue reported by a commercially licensed client. and removed support:3 An issue reported by a commercially licensed client. labels Feb 23, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@engineering-this engineering-this

Labels
status:confirmed An issue confirmed by the development team. support:1 An issue reported by a commercially licensed client. target:minor Any docs related issue that can be merged into a master or major branch. type:bug A bug.
Projects
None yet
Milestone
4.11.4
Development

No branches or pull requests
5 participants
@f1ames @jswiderski @mlewand @engineering-this @lslowikowska