[Question] MonologBundle + long running process about monolog-bundle HOT 5 CLOSED

I just had a quick look and found out that memory leaks in the Symfony\Bridge\Monolog\Handler\DebugHandler (or actually in its base class - Monolog\Handler\TestHandler).

Adding --no-debug to your command in combination with buffer_size will prevent memory leaks.

from monolog-bundle.

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

from monolog-bundle.

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:

monolog:
    handlers:
        main:
            type:         fingers_crossed
            action_level: error
            handler:      nested
            buffer_size:  30
        nested:
            type:  stream
            path:  "%kernel.logs_dir%/%kernel.environment%.log"
            level: error

And the command runs in prod mode , over 16h now and stable.

I will close this issue now.

from monolog-bundle.

@jakzal Do you remember what the memory leak was in TestHandler, or if it was fixed and if so, in which version of monolog?

from monolog-bundle.

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:

monolog:
    handlers:
        main:
            type:         fingers_crossed
            action_level: error
            handler:      nested
            buffer_size:  30
        nested:
            type:  stream
            path:  "%kernel.logs_dir%/%kernel.environment%.log"
            level: error

And the command runs in prod mode , over 16h now and stable.

I will close this issue now.

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?

from monolog-bundle.