Bug #83507

Max allowed memory size on FileBrowser.php when trying to implode 36.663 lines

Added by elias almost 3 years ago. Updated 7 months ago.

Should have
Target version:
Start date:
Due date:
% Done:


TYPO3 Version:
PHP Version:
Is Regression:
Sprint Focus:


After a legacy project migration on a live intranet site with lot of files, the _migration/content_uploads/ folder has 36.663 files. When trying to access via FileBrowser from an standar content, always show a max allowed memory size on line 360 of file TYPO3\CMS\Recordlist\Browser\FileBrowser.php.

359:    <table class="table table-striped table-hover" id="typo3-filelist">
360:            ' . implode('', $lines) . '
361:    </table>';

So the implode function result on a memory problem on a server with 1G of memory dedicated to PHP, the server can process mime info, iterate over the files and metadata on FAL, but it crash on a simple implode. I think that this is a bug because the migration tools have move the files to that folder and is not a very strange scenario with alive projects with thousand of files.

I think this must be solved with a basic pagination but seems that it is implemented on DatabaseBrowser.php but not on FileBrowser.php.

What do you think?

Related issues

Related to TYPO3 Core - Feature #64764: FileList and ElementBrowser must implement a paginate system for files Accepted 2015-02-02


#1 Updated by Riccardo De Contardi over 1 year ago

  • Related to Feature #64764: FileList and ElementBrowser must implement a paginate system for files added

#2 Updated by Susanne Moog 7 months ago

  • Status changed from New to Closed

Pagination would be the way to go and is handled in #64764 - let's continue there. Going to close the issue here to keep the topics together.

Also available in: Atom PDF