Req #61698 [Opn]: Memory exhausted - unable to investigate

Edit report at https://bugs.php.net/bug.php?id=61698&edit=1 ID: 61698 User updated by: mick at deafzone dot ch Reported by: mick at deafzone dot ch Summary: Memory exhausted - unable to investigate Status: Open Type: Feature/Change Request Package: *General Issues Operating System: Linux PHP Version: 5.3.10 Block user comment: N Private report: N New Comment: Correction, I'm specifying the path to the error log file already in the htaccess file like that: php_value error_log [PATH TO LOG FILE] I can I force it to generate a backtrace as well with another parameter? Previous Comments: ------------------------------------------------------------------------ [2012-04-12 03:34:45] mick at deafzone dot ch Description: ------------ Hello there I'm Michael from www.binarykitchen.com - for one of my websites I see very strange PHP Fatal Errors in the log file I have specified in ini_set('error_log', $logFile); It always contains entries like these: [11-Apr-2012 20:18:11 UTC] PHP Fatal error: Allowed memory size of 201326592 bytes exhausted (tried to allocate 523800 bytes) in /var/www/[...]/File.php on line 424 Line is not always 424, it's mostly random. I know somewhere an error is thrown and the code is somewhat in an endless loop. Must be a bug in my code but I can't find it. There are over 2000 classes heh. I really need a backtrace. Or more debugging information. Hence I wonder if error_log could produce more information for me? Any ideas or suggestions are welcome. Sorry to post this issue at the wrong place but I don't know where else to ask but to address to the PHP Core Devs directly. Thanks heaps for your advice. Cheers Michael ------------------------------------------------------------------------ -- Edit this bug report at https://bugs.php.net/bug.php?id=61698&edit=1