#32002 [Com]: FATAL erealloc() Restarts

From: Date: Wed, 07 Sep 2005 18:52:22 +0000
Subject: #32002 [Com]: FATAL erealloc() Restarts
References: 1  Groups: php.bugs 
Request: Send a blank email to php-bugs+get-84642@lists.php.net to get a copy of this message
ID: 32002 Comment by: jeffdripps at isegames dot com Reported By: tlamay at cte1 dot com Status: No Feedback Bug Type: Unknown/Other Function Operating System: Windows 2003 PHP Version: 4CVS-2005-02-17 New Comment: Using 4.4.1 binary this problem occurs and the process restarts as soon as the first *.php file is requested. PHP 4.4.1 is unusable on a multiprocessor machine running W2K and Apache2. Previous Comments: ------------------------------------------------------------------------ [2005-03-05 01:00:08] php-bugs at lists dot php dot net No feedback was provided for this bug for over a week, so it is being suspended automatically. If you are able to provide the information that was originally requested, please do so and change the status of the bug back to "Open". ------------------------------------------------------------------------ [2005-02-25 15:15:08] jorton@php.net Not enough information was provided for us to be able to handle this bug. Please re-read the instructions at http://bugs.php.net/how-to-report.php If you can provide more information, feel free to add it to this bug and change the status back to "Open". Thank you for your interest in PHP. The FATAL message correspond to Zend calling exit(), which kills all the threads in the process, so that much is expected. To track down the memory issues you could add to your LogFormat directive: "%{mod_php_memory_usage}n" - this will log the maximum number of bytes allocated during each particular request. ------------------------------------------------------------------------ [2005-02-22 21:28:44] jonohlsson at hotmail dot com must say i have this exact problem myself running win 2k / apache 1.3.33 / php 4.3.10 / Zend optimizer 2.5.7 and phpBB forum the apache log is filled with those erealloc errors and the browser page goes blank with a "server not found" message ...but i think it only happens if browsing with IE. mozilla works fine. weird isn't it? i've also tried changing php.ini memory settings, but this deosn't affect the apache log at all ------------------------------------------------------------------------ [2005-02-17 20:46:17] tlamay at cte1 dot com Okay, after a bit of tweaking I got the latest PHP5 running. It crashes within 8-10 minutes. I have since migrated back to 4.3.10, the most stable version for me at the moment. Funny thing about the PHP5...when it crashes, Apache doesn't ever restart. The server stays completely down. I have to physically start it again. This behavior doesnt occur in 4.3.x. Thu Feb 17 14:31:26 2005] [notice] Parent: Created child process 6672 [Thu Feb 17 14:31:26 2005] [notice] Disabled use of AcceptEx() WinSock2 API [Thu Feb 17 14:31:35 2005] [notice] Child 6672: Child process is running [Thu Feb 17 14:31:35 2005] [notice] Child 6672: Acquired the start mutex. [Thu Feb 17 14:31:35 2005] [notice] Child 6672: Starting 750 worker threads. [Thu Feb 17 14:31:35 2005] [notice] Child 6672: Listening on port 443. [Thu Feb 17 14:31:35 2005] [notice] Child 6672: Listening on port 443. [Thu Feb 17 14:31:35 2005] [notice] Child 6672: Listening on port 80. [Thu Feb 17 14:31:35 2005] [notice] Child 6672: Listening on port 80. FATAL: erealloc(): Unable to allocate 98304 bytes [Thu Feb 17 14:39:29 2005] [notice] Parent: child process exited with status 1 -- Restarting. ------------------------------------------------------------------------ [2005-02-17 05:25:51] sniper@php.net Please try using this CVS snapshot: http://snaps.php.net/php5-latest.tar.gz For Windows: http://snaps.php.net/win32/php5-win32-latest.zip Please try the latest HEAD too so we'll see if this is any better there (some memleak fixes exist there which were not allowed to be backported to PHP_4_3 branch) ------------------------------------------------------------------------ The remainder of the comments for this report are too long. To view the rest of the comments, please view the bug report online at http://bugs.php.net/32002 -- Edit this bug report at http://bugs.php.net/?id=32002&edit=1

« previous php.bugs (#84642) next »