Yes inadequate resources would be my concern also, if it were to occur in other cases. I'm using a hosting provider which was recommended as a symfony friendly provider on the website. They have provided very good support so far. They told me the next time the problem happens, they can monitor it live to see what is occurring. I will probably try to recreate the issue in the next few days, when I make any non- reverse compatible database changes..
It's only in loadData that I deal with a large number of rows like this. Cross your fingers, but it should only happen for me in this situation, and I only need to load the data once. Cheers, Steve On Jun 11, 8:35 am, Gareth McCumskey <[email protected]> wrote: > The OP did say that the problem seemed intermittent. If it was a problem > with Propel or symfony then it would be consistent unless the OP is > constantly editing Propel or symfony code between runs. > > Could it be that being on a shared host that the memory usage settings are > related to other users as well? THis would explain the randomness of the > results as you cannot control what memory other users might be consuming. > > If this -is- the case, then you need to seriously consider changing hosts as > this is not a good problem to be having and there are plenty of others out > there. Hell if your so inclined even look at services like linode.com where > you can setup your own server very cheaply > > > > On Thu, Jun 11, 2009 at 8:54 AM, pghoratiu <[email protected]> wrote: > > > Hi! > > > I had some problems also with php memory collection, the main problem > > was with circular reference used in propel when dealing objects. > > > 1. Circular reference - having two related objects A, B the following > > will generate a memory leak becase A is referencing object B and B is > > referencing object A at the same time: > > A->add(B); > > A->save(); > > > but if you save each object one by one without trying to save them at > > once it should work fine: > > A->save() > > B->setWhateverId(A->getId()) > > B->save() > > > When you have a php script running on the server web server it's not a > > big problem because the process completes quickly and all alocated > > memory is released, problems are usually with CLI and long running > > processes. > > > 2. Another thing to watch out if you manipulate large number of > > objects within a function, the objects are released only after the > > function completes. This depends on the given situation, i did not > > encounter problems with this myself. > > > gabriel > > > On Jun 10, 9:25 pm, Nickolas Daskalou <[email protected]> wrote: > > > Could be due to PHP's garbage collection not working properly on some > > types > > > of objects. I remember reading about it a while ago, not sure if there is > > a > > > fix for it yet. > > -- > Gareth McCumskeyhttp://garethmccumskey.blogspot.com > twitter: @garethmcc --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
