-
-
Notifications
You must be signed in to change notification settings - Fork 1.9k
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
bug: OOM errors on stream handler as of Monolog 2.3.0 #1577
Comments
I Will create a PR during The morning... to propose a solution for this |
The pull request is created but it cannot pass a phpstan test, and I dont know if is my change or something else. Any help? |
MohammedAttya2
added a commit
to MohammedAttya2/framework
that referenced
this issue
Aug 17, 2021
Monolog 2.3.0+ produces `PHP Fatal error: Allowed memory size of 2147483648 bytes exhausted (tried to allocate 2147483647 bytes)` Seldaek/monolog#1577
Should be fixed by #1578 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Monolog version 2 (only on 2.3.0+)
Error:
PHP Fatal error: Allowed memory size of 2147483648 bytes exhausted (tried to allocate 2147483647 bytes) in...
This can be recreated with the following file (note the php ini setting
memory_limit=2048M
):@dwsupplee tracked the issue down to this change. When I remove the calls to
stream_set_chunk_size
in the handler, the OOM error disappears.I don't know the proper solution, if this change should just be reverted, or if we should do something to ensure the memory limit is less than the chunk size... maybe there's some specific handling necessary for
tmpfile
? Either way, this is a pretty nasty error so any help is appreciated!The text was updated successfully, but these errors were encountered: