-
-
Notifications
You must be signed in to change notification settings - Fork 234
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
[Question] MonologBundle + long running process #118
Comments
I just had a quick look and found out that memory leaks in the Adding |
Thanks. The issue occurred in prod mode, which deactivates the debug. Seems to work after reinstalling monolg-bundle 2.7.1, maybe there was something wrong with my installation. This is how my prod config looks like at the moment:
And the command runs in prod mode , over 16h now and stable. I will close this issue now. |
I don't want to reopen a closed issued but I too had the same issue http://stackoverflow.com/questions/35977213/memory-leak-symfony-and-monolog-and-console/35977531#35977531 |
@jakzal Do you remember what the memory leak was in TestHandler, or if it was fixed and if so, in which version of monolog? |
Hey @tiborb , you changed the level of the nested handler from debug (collecting all messages) to error (allowing the nested handler to discard all debug and warning messages). Maybe the leak was not resolved, but just your configuration prevented the leak to occur? |
I have a long running console command for testing:
and my prod config looks like this:
The elements in the buffer do not exceed the limit, but the overall memory usage of the process is still increasing with every iteration.
If I let the process run for a few minutes it gets over 1gb and i have no idea where the memory increase comes from.
I also did some profiling with xdebug but it doesn't help too much:
Any help would be much appreciated,
Tibor
The text was updated successfully, but these errors were encountered: