Hey Adam, maybe you can clear the log after every successful execution of whatever your task does. After all, this handler only keeps the info stuff in case there is an error, so if there's no error, just dump the info.. Just a thought.
Daniel On Friday, July 13, 2012 8:27:49 PM UTC-7, Adam Monsen wrote: > > Thanks for your reply, Stof. > > Sounds like the scenario I described could definitely lead to a memory > leak. > > On 07/13/2012 02:57 PM, Christophe COEVOET wrote: > > The FingersCrossedHandler has an optional buffer limit. My advice would > > be to run your long running processes in a dedicated environment > > (importing the prod config as basis for instance) in which you can tweak > > some config (for instance adding a buffer limit on this handler). FYI, > > the configuration reference of MonologBundle (showing all possible > > options) is available on > > http://symfony.com/doc/current/reference/configuration/monolog.html > > > > Symfony being a web framework, I don't think expecting long running > > processes for the prod environment is a the best expectation (your user > > will leave your site quickly if the process to generate it can be > > considered as long running). And as it supports environments, it is easy > > to have a separate environment with a configuration optimized for long > > running processes. > > Yep, I'm describing a daemon running in the background. Async only. > Users would never be waiting for this daemon to do anything. > > -- 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 [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/symfony-devs?hl=en
