Bug #83507

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

Added by elias 11 months ago.

Status:
New
Priority:
Should have
Assignee:
Category:
-
Target version:
-
Start date:
2018-01-08
Due date:
% Done:

0%

TYPO3 Version:
7
PHP Version:
5.6
Tags:
Complexity:
Is Regression:
Sprint Focus:

Description

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?

Also available in: Atom PDF