-
-
Notifications
You must be signed in to change notification settings - Fork 33
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
Fatal error: Allowed memory size of ... bytes exhausted (tried to allocate ..bytes) #151
Comments
How high is a PHP process memory? How many log entries are there in the database? |
Hi, |
…log entries #151 [TER-187] [TER-188]
Same Problem here. I'm using Version 6.0.1 on TYPO3 12. |
We are working on a solution, see PR #198. Version 6.0.2 is coming soon. |
Thanks for your great Work. I Just wondered If #198 is the same problem. It seems the whole File is read into the response at once. This is too much memory usage. I looked at your code but found no way to work around this. I found other discussion on how to do such things with extbase. But i did not find a solution until now. |
I think you mean a different problem. This problem concerns the download of the logs in the backend. And this problem is currently being fixed. |
OK, sorry. |
Yes, please create a new issue. I assumed that this error would no longer occur with 5.x or 6.x. Strange |
* [TASK] Performance improvement for backend module with many download log entries #151 [TER-187] [TER-188] * [TASK] Add second parameter for integer values in createNamedParameter #151 [TER-187] [TER-188] * [BUGFIX] Use \PDO::PARAM_INT instead of \PDO::INT #151 [TER-187] [TER-188] * [TASK] Prepare release of version 5.0.4 [TER-187] [TER-188]
Describe the bug
If I click on the backend on "download traffic", PHP runs out of memory.
So the problem is, that the default tries to load all entities from database, what causes the memory problem.
So it would be great, if there would be a default, that does not load everything ;-)
Environment (please complete the following information):
The text was updated successfully, but these errors were encountered: