Hi Avnish, Thanks for your reply!
We were experiencing this with 1.2.8. Then, we moved to 1.2.7 to see if that fixed the error, but no luck. This error happens even with 128 MB per process, so I guess that it's sf who's taking so much memory (maybe this function might get recursive?). Another interesting thing is that even when the process is halted - as it is b/c of this fatal error - you can browse our site without noticing it. However, apache drains the server memory and we must reboot. Right now, I just commented that line. I'm using Propel, however I'll apply the patch and see how it works. It doesn't happen on stage or on our dev's pcs... it happens only @ production - I guess it's b/c of the traffic volumes. I'll wait till Monday to apply it... that's something we learnt from our mistakes... never put a non critical change up a fridayx On 31 jul, 17:01, Avnish Pundir <[email protected]> wrote: > Which version of symfony are you using? > I was seeing similar error while I was using (symfony 1.2.4) cache with > doctrine forms. Then I found following > bughttp://trac.symfony-project.org/ticket/5814- which apparently is fixed > in 1.2.7 > You may want to switch to 1.2.8 and see if it fixes your error!! > > From your error message itself it's clear that serilized object is > using around 8.5M (out of 32MB) memory - needless to say more than 24M > has already been consumed by application before execution reached to > this point. > > -------- Original Message -------- > Subject: [symfony-users] Running out of memory when creating the cache > From: Gervasio <[email protected]> > To: symfony users <[email protected]> > Date: Saturday 01 August 2009 12:13 AM > > > Hi! > > > I posted this on the forum, but got no replies. Probably the list is > > the place to get more feedback ;) > > > We have a decently big app, and we have our max_memory limit on 32 MB, > > however this is an issue that happened when we had 128 MB too. > > > When I see the error log from apache, I see a lot of > > > [Thu Jul 23 09:56:15 2009] [error] [client XXX.XXX.XXX.XXX] PHP Fatal > > error: Allowed memory size of 33554432 bytes exhausted (tried to > > allocate 8711424 bytes) in /path/to/app/cache/frontend/prod/config/ > > config_core_compile. yml.php on line 3365 > > > We're also seeing some weird issues that are fixed just by clearing > > the cache, so my guess is that some cache files might get corrupted > > when this fatal error happens. > > > I thought we might run the cache generator each say, 12 hours in a > > cron with a higher memory_limit, but then I'd like to disable the > > cache generation when the app runs - if the cache is generated, just > > use it. Otherwise, just open the yml files as the _dev does. Do you > > know how can I: > > > 1) Generate the cache in a cron > > 2) Disable the cache generation on the app > > > This is the function that causes the memory failure. > > > public function shutdown() > > { > > if (!is_null($this->cache) && $this->cacheChanged) > > { > > $this->cacheChanged = false; > > $this->cache->set('symfony.routing.data', serialize($this- > >> cacheData)); > > } > > } > > > The line 3365 is > > > $this->cache->set('symfony.routing.data', serialize($this- > >> cacheData)); > > > Thanks in advance! --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "symfony users" 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-users?hl=en -~----------~----~----~----~------~----~------~--~---
