+1
Perhaps this is why my Symfony tasks that need an application
environment produce such a flood of unwanted debugging output to the
console, even if I call sfConfig::set('sf_logging_enabled', false) and
friends?
On Tue, Feb 2, 2010 at 7:35 PM, Tony Piper <[email protected]> wrote:
>
>
> On Feb 2, 8:39 pm, Brandon Turner <[email protected]> wrote:
>> Devs,
>>
>> This is my first post to the symfony-devs list. It is not intended to
>> be a "how do I do xxx" post, so I apologized if it is perceived as such.
>
> Just to lend my support to Brandon's post: I'm having the same problem
> and have spent about 4 hours trying to figure out why I was having
> such huge memory usage in what was supposed to be a long-running task.
>
> I certainly can't see the point of creating an
> ApplicationConfiguration with 'debug=true' - after all, there's no
> debug toolbar in a task environment...
>
> Thanks for any insight you can give us...
>
> cheers,
>
> Tony.
>
> --
> 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.
>
>
--
Tom Boutell
P'unk Avenue
215 755 1330
punkave.com
window.punkave.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.
