Uploaded image for project: 'Hippo CMS'
  1. Hippo CMS
  2. CMS-8001

CKEditor does not destroy editor instances when document is discarded (client-side memory leak)

    XMLWordPrintable

Details

    • Bug
    • Status: Closed
    • Top
    • Resolution: Fixed
    • 2.26.00
    • 2.26.04
    • None
    • Sprint 83, Sprint 84

    Description

      When an edited document is discarded, the CKEditor instances used in the document are not destroyed.

      Steps to reproduce:
      1. login to the archetype CMS
      2. edit a news document
      3. discard the document by clicking the red cross in the document's tab
      4. open the JavaScript console (F12 in Chrome)
      5. type "CKEDITOR.instances" and hit <enter>

      Expected: an empty JavaScript object is logged
      Actual: a JavaScript object with one element is logged

      Background: the global JavaScript variable CKEDITOR.instances contains a map (editor ID -> editor instance) of all open CKEditor instances. Each instance should be destroyed when the associated <textarea> element is removed from the DOM (see CKEditorPanel.js#destroyEditorWhenElementIsDestroyed). This works fine when a document is "saved & closed", but not when a document is discarded.

      Attachments

        Activity

          People

            Unassigned Unassigned
            mdenburger Mathijs den Burger (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: