No – it´s not the problem:
the memory shouldn´t be increased, the unused things should be
dealloced!
On Nov 26, 4:47 pm, "Pablo Godel" <[EMAIL PROTECTED]> wrote:
> what's your memory limit ?
>
> Pablo
>
> On Tue, Nov 25, 2008 at 3:35 PM, Fabian Spillner
>
> <[EMAIL PROTECTED]> wrote:
>
> > I wonder, how the symfony core team deal with memory management on
> > symfony.
>
> > If I write an example task like that, it fails with memory out error:
>
> > <?php
>
> > class MemoryOutTask extends sfBaseTask
> > {
> > protected function configure()
> > {
> > $this->namespace = 'test';
> > $this->name = 'memory-out';
>
> > $applicationConfiguration =
> > ProjectConfiguration::getApplicationConfiguration('your-app', 'cli',
> > true);
> > sfContext::createInstance($applicationConfiguration);
> > }
>
> > protected function execute($arguments = array(), $options = array())
> > {
> > $browser = new sfBrowser();
> > $index = 0;
>
> > while (true)
> > {
> > $browser->get('/?v=' . $index);
> > $index++;
>
> > if ($index % 10)
> > {
> > $this->logSection('memory', memory_get_usage());
> > }
> > }
> > }
> > }
>
> > And I got the same problem with propel and more things.
>
> > It would be nice, if memory management will be a part not to be
> > ignored for next releases.
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
