Skip to content

Check for potential memory leaks  #589

Closed
@jswiderski

Description

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

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Labels

status:confirmedAn issue confirmed by the development team.support:1An issue reported by a commercially licensed client.target:minorAny docs related issue that can be merged into a master or major branch.type:bugA bug.

Type

No type

Projects

No projects

Milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions