Issue Bug Closed

#91257Serious performance issues due to detached DOM nodes

Andreas Kienast 05/01/20, 15:46 updated 09/16/26, 05:55

Description

The TYPO3 backend suffers from heavy performance issues. Using the backend for ~1 hour made it really unusable, as the browser’s garbage collection kicks in after every second click and occupies more and more time and blocks the browser from doing its work.

After creating a few heap snapshots I found out we create a lot of detached DOM nodes.

For explanation: a detached DOM node is a node referenced in JavaScript, but not rendered the actual DOM. Such references don’t get removed and occupy memory over time.
In DebugConsole, for example, the nodes are created but not rendered initially: https://github.com/TYPO3/TYPO3.CMS/blob/master/Build/Sources/TypeScript/backend/Resources/Public/TypeScript/DebugConsole.ts#L115

I’ve created several screenshots of the profiles, the only thing I did is opening the EditDocumentController for different content elements multiple times and closing them again and browsing in the page tree.

Since the snapshot files are too large to be attached in Forge, I’ve uploaded them to Google Drive: https://drive.google.com/open?id=1-XiCT13VlWbNBfIY-QrgAbTpta54MpEA

Reviews 0

No change resolves or names this issue in its commit message, and no comment links one.

Files 5

History 6

  1. Oliver Hader commented and changed attached closure_size.png attached closure_details.png <span data-processor="relativetime" data-value="2020-05-01T17:43:27+00:00" > 05/01/20, 17:43 </span>

    In my environment memory consumption on detached nodes is not that high… but closure and object stack is (see screenshots) e.g. referring to ShortcutMenu or t3-topbar-update..

  2. Benni Mack commented and changed status New Needs Feedback <span data-processor="relativetime" data-value="2025-03-23T19:19:58+00:00" > 03/23/25, 19:19 </span>

    Do we still have this problem in v13?

  3. Andreas Kienast commented and changed status Needs Feedback Closed <span data-processor="relativetime" data-value="2026-09-16T05:55:34+00:00" > 09/16/26, 05:55 </span>

    Probably invalid by now since jQuery is gone for good.