Le 24/08/2011 17:11, Oleg Stepura a écrit :
hi!
I call it a leak since it's hard to find out why this happens and then
it's impossible to somehow manipulate or disable collecting. When used
memory increases and you cannot control it - it's a leak.
I clearly understand what it is doing, but don't really think you will
try to analyze 3000 records from web panel (simply your browser will
hang).
Personally I used a solution to replace the symfony's logger with my
own instance which does not have lots of handlers inside and since
that does not leak.
But this took some time to refactor existing code that uses logger
(with all used classes which also uses Logger) with logger setters and
getters.
This however breaks Dependency Injection principles.
Thanks!
Why do you need to change all code that uses the logger ? If you want to
use a different implementation, simply create a class implementing the
Symfony\Component\HttpKernel\Log\LoggerInterface and use it to define
the logger service.
As Symfony is based on the DI pattern, you can replace the
implementation very easily as long as you implement the needed
interface. (Btw, changing from Zend\Log to Monolog several months ago
did not require changing the code using the logger)
--
Christophe | Stof
--
If you want to report a vulnerability issue on symfony, please send it to
security at symfony-project.com
You received this message because you are subscribed to the Google
Groups "symfony developers" group.
To post to this group, send email to symfony-devs@googlegroups.com
To unsubscribe from this group, send email to
symfony-devs+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/symfony-devs?hl=en
