-
Notifications
You must be signed in to change notification settings - Fork 40
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
PHP out of memory when using the search in File Browser with TYPO3 v11.5 #125
Comments
Same Problem. Fatal error: Allowed memory size of 1073741824 bytes exhausted (tried to allocate 4096 bytes) in /var/www/html/packages/aus_driver_amazon_s3/Classes/Driver/AmazonS3Driver.php on line 803 |
@mmunz In my case there was a folder in the root directory and the name was just "/" that was causing this issue. |
@mmunz @MohsinQK Also the caching framework is used and could help. For examle it could be persistent and controlled by any other application managingn the Data in S3. Please leave a comment if that helps. |
@MohsinQK thanks, but i don't have such a folder. Just many files in the root of the bucket and 5 folders. |
@weakbit i've now tested feature/performance-improvements-caching:
|
Thanks for pointing this out! Could you please check if this solves the issue? |
@Lagerregal the search result is loading now with 512M memory limit. It is still not fast (80s), but the OOM is gone. |
Version: aus_driver_amazon_s3 v1.12.1
TYPO3 v11.5.26
PHP: 8.2.3
We have a S3 bucket with around 100000 files.
In TYPO3 to 11.5 we experience out of memory errors when using the search for Files in the File Browser (above the file tree):
The search calls the endpoint /typo3/ajax/filestorage/tree/filterData?token=xyz&q=searchTerm with ajax.
Raising the memory limit to 1G still runs into the memory limit.
Raising the limit to 2G the filter works, but needs about 220s to finish.
This issue is likely related to #124
And yes, as you can see from the exception we run a bit a special setup mixed up with symfony, but i'm relatively confident that this is not the cause of these issues, because backend code is rarely touched and should run independently.
The text was updated successfully, but these errors were encountered: