I have done something similar and the memory leak problem was difficult to solve. In my case it was due to circular references between objects and I always had to use unset() explicitely on individual objects after saving them into the database. Make sure the objects you are trying to save do not reference each other because they can not be free-d by the PHP garbage collector, also PHP 5.3 is somewhat smarter about memory recycling (compared to PHP 5.2).
If you can not figure out where the problem is you should go with SQL data inserts. gabriel On Jun 2, 6:00 pm, f1gm3nt <f1gm...@gmail.com> wrote: > I'm looking into doing batch imports with a symfony task. The issues > I'm having are seg faults and running out of memory. Even after > jacking the memory limit to 2gigs. Has anyone else ever done batch > imports using a symfony task that can shed some light on how they did > it? > > -f1g -- 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 users" group. To post to this group, send email to symfony-users@googlegroups.com To unsubscribe from this group, send email to symfony-users+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/symfony-users?hl=en
