Issue Bug Closed

#107567Fatal error in DebuggerUtility.php after commit e6aaf8754e39c1b9b9bc1d747bb115e40eddfb64 - Task #105035 - Memory exhausted with f:debug ViewHelper

Devid Messner 09/30/25, 10:43 updated 09/30/25, 12:57

Description

Since commit e6aaf8754e39c1b9b9bc1d747bb115e40eddfb64 in TYPO3 v13, the f:debug Fluid ViewHelper causes fatal memory errors when used with large datasets.

**Error Message:**
```
Fatal error: Allowed memory size of 2147483648 bytes exhausted (tried to allocate 85188048 bytes) in /var/www/html/vendor/typo3/cms-extbase/Classes/Utility/DebuggerUtility.php on line 444
```

**Steps to Reproduce:**
1. Use the f:debug ViewHelper in a Fluid template with large amounts of data
2. The fatal error occurs immediately

**Additional Information:**
- This issue appeared after commit: https://github.com/TYPO3/typo3/commit/e6aaf8754e39c1b9b9bc1d747bb115e40eddfb64
- Before this commit, the f:debug ViewHelper worked correctly with the same large datasets
- The issue seems to be related to memory handling changes in the DebuggerUtility class

Reviews 0

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

History 3

  1. Devid Messner commented and changed subject Fatal error in DebuggerUtility.php after commit e6aaf8754e39c1b9b9bc1d747bb115e40eddfb64 - Memory exhausted with f:debug ViewHelper Fatal error in DebuggerUtility.php after commit e6aaf8754e39c1b9b9bc1d747bb115e40eddfb64 - Task #105035 - Memory exhausted with f:debug ViewHelper <span data-processor="relativetime" data-value="2025-09-30T12:08:18+00:00" > 09/30/25, 12:08 </span>

  2. Garvin Hicking commented and changed status New Closed <span data-processor="relativetime" data-value="2025-09-30T12:57:51+00:00" > 09/30/25, 12:57 </span>

    Yes, the patch “buffers” output some more and needs more memory. For debugging you will need to allow
    PHP more memory, or even better for large results you should use xdebug instead.

    Because this memory usage will likely not be changed, I’m afraid we’ll need to reject this case, I hope you can understand?

    The debugging in fluid is more aimed at easy integration of “smaller” result sets.