ID:               36017
 Updated by:       [EMAIL PROTECTED]
 Reported By:      Brian dot White at foxfire74 dot com
-Status:           Open
+Status:           Feedback
 Bug Type:         Apache2 related
 Operating System: Windows XP SP2
 PHP Version:      4.4.2
 New Comment:

Please try using this CVS snapshot:

  http://snaps.php.net/php5.1-latest.tar.gz
 
For Windows:
 
  http://snaps.php.net/win32/php5.1-win32-latest.zip




Previous Comments:
------------------------------------------------------------------------

[2006-01-15 01:48:53] Brian dot White at foxfire74 dot com

Description:
------------
Apache2 crashes after upgrading to PHP 4.4.2.  THe following is found
in the Apache's error log.

[Sat Jan 14 12:15:11 2006] [notice] Parent: child process exited with
status 3221225477 -- Restarting.
[Sat Jan 14 12:15:12 2006] [notice] Apache/2.0.55 (Win32) PHP/4.4.2
configured -- resuming normal operations
[Sat Jan 14 12:15:12 2006] [notice] Server built: Oct  9 2005 19:16:56
[Sat Jan 14 12:15:12 2006] [notice] Parent: Created child process 3700
[Sat Jan 14 12:15:14 2006] [notice] Child 3700: Child process is
running
[Sat Jan 14 12:15:14 2006] [notice] Child 3700: Acquired the start
mutex.
[Sat Jan 14 12:15:14 2006] [notice] Child 3700: Starting 250 worker
threads.

This only happens on my production system where MySQL is also
installed.  Everything works as expected on the test machine (which
connects  to the production database server).

Reproduce code:
---------------
All of my PHP apps crash.  Unfortunately, the index.php files are quite
large.  I have not yet isolated the offending code but I wanted to enter
a bug report since before others upgrade since 4.4.2 is a new release.

Expected result:
----------------
Page returned as expected without Apache2 crashing.

Actual result:
--------------
Browser shows the entire page but is still waiting for additional
input.


------------------------------------------------------------------------


-- 
Edit this bug report at http://bugs.php.net/?id=36017&edit=1

Reply via email to