If error occurs on shutdown it definitely caused by some destructor. I've looked into all defined by cake core destructors and found some possible dangerous in some cases. All of them write caches and use array_filter($objects_to_save) that may give memory allocation error if $objects_to_save is a large array and memory is not enough. Configure writes objects map, App writes dirs map and files map and I18n writes domains map.
Also ConnectionManager closes session. Own session handler code may also have dangerous operations. DataSource closes connecton, custom datasource may have dangerous code. On Mar 12, 3:10 pm, Mark Hindley <m...@hindley.org.uk> wrote: > On Thu, Mar 11, 2010 at 09:01:26AM -0800, Dr. Loboto wrote: > > If your production runs with debug = 2 it may be big SQL log and new > > allocation to show it. But I'm not sure. > > Thanks. The production was running with debug = 0. When it is set to 2, > the Fatal Error appears after the SQL log is output, so it doesn't > appear to be that. > > Any other suggestions of how to get a handle on this? > > My understanding is you can't trap Fatal Errors like this to get a > backtrace. The error message doesn't give a location. I don't even know > where to start looking! > > Cheers, > > Mark Check out the new CakePHP Questions site http://cakeqs.org and help others with their CakePHP related questions. You received this message because you are subscribed to the Google Groups "CakePHP" group. To post to this group, send email to cake-php@googlegroups.com To unsubscribe from this group, send email to cake-php+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/cake-php?hl=en
