I was having a similar problem with the cake debugger running out of
memory on an error (in this case it was an undefined variable in the
view). I just commented out the offending lines of code in /cake/libs/
debugger.php. The problem was a call to the get_class() function and
it looks like it's happening with you on line 414 as well. I'd try
commenting out the following:

//if(in_array($serialized, $history, true)) {
//       $value = ife(is_object($value), "*RECURSION* -> " .
get_class($value), "*RECURSION*");
//}

and see if it starts behaving.

Dave

On Jan 23, 1:54 pm, jonknee <[EMAIL PROTECTED]> wrote:
> I recently upgraded to v1.2 and have been playing around to get Smarty
> working (which is how I was using Cake 1.1). It's going fine except
> when I call a variable that doesn't exist... Smarty throws the
> 'Undefined index' error that should be no problem (and in most cases
> not be seen), but Cake's debugger takes over and gets stuck in a loop.
> The httpd process takes 100% of the CPU and 30 seconds later I see a
> message that the script was halted because the maximum execution time
> was exceeded.
>
> > [error] PHP Fatal error:  Maximum execution time of 30 seconds exceeded in 
> > /Library/WebServer/cake/cake/libs/debugger.php on line 414
>
> Any ideas on how I could either see what the code is choking on or how
> to let Smarty opt-out of the Cake error sequence?
>
> The compiled Smarty code that's causing this comes out looking like:
>
> <?php echo $this->_tpl_vars['variable_name']; ?>
>
> If $this->_tpl_vars['variable_name'] isn't defined the whole thing
> goes into the endless loop and I have to kill the process or wait it
> out.
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "Cake 
PHP" 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/cake-php?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to