Issue Bug Closed

#93230TYPO3 memory issues when changing slugs

Dennis Prinse 01/06/21, 10:52 updated 10/06/26, 07:36

Description

TYPO3 v10 has the feature to change the slug of its subpages when you change the slug of a page. That’s exactly what I want TYPO3 to do, however this recursive update is not working when editing a page which has many subpages. In my case, when I edit one of the higher level pages (which has 500+ subpages) TYPO3 runs out of memory and the update is aborted. The slug cannot be changed it seems.

A side effect of this issue is that redirects are being generated because the data handler isn’t used to generate them (see #91792). What happens is that pages which have been processed by TYPO3 for the slug update do have a redirect, however because the slug for that page hasn’t changed yet in the database (and other places) the page is unresolvable and leads to the 404 error page. To resolve the non-working redirects, I go to the root in the list module and search for the new slug and remove all of the redirects that have been created. This resolves the issue of the non-working redirects, however the problem still exists for changing the slug.

Reviews 0

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

History 3

  1. Benni Mack commented and changed status New Closed <span data-processor="relativetime" data-value="2026-10-06T07:36:29+00:00" > 10/06/26, 07:36 </span>

    The memory problem as reported is gone on current main: changing the slug of a page with 500+ subpages no longer runs out of memory. Memory use still grows with the number of subpages, though, so a very large tree could in theory still hit the limit.

    I wrote a throwaway functional test that sets up a page tree, changes the parent’s slug through DataHandler (the same path as editing it in the backend) and records memory and run time:

    ┌──────────┬───────────────┬───────────────────┬───────────┬───────────────────┬──────────────────────────────┐
    │ Subpages │ Slugs updated │ Redirects created │   Time    │ Extra peak memory │ Memory still held afterwards │
    ├──────────┼───────────────┼───────────────────┼───────────┼───────────────────┼──────────────────────────────┤
    │ 60       │ 60            │ 61                │ 0.15 s    │ 2.0 MB            │ 1.7 MB                       │
    ├──────────┼───────────────┼───────────────────┼───────────┼───────────────────┼──────────────────────────────┤
    │ 220      │ 220           │ 221               │ 0.5 s     │ 4.9 MB            │ 4.4 MB                       │
    ├──────────┼───────────────┼───────────────────┼───────────┼───────────────────┼──────────────────────────────┤
    │ 630      │ 630           │ 631               │ 1.4–1.8 s │ 13.2 MB           │ 12.2 MB                      │
    └──────────┴───────────────┴───────────────────┴───────────┴───────────────────┴──────────────────────────────┘

    At the 630-subpage size, every slug was rewritten and every redirect created, and peak memory rose by only 13 MB.

    I will close this issue now.