|  support |  documentation |  report a bug |  advanced search |  search howto |  statistics |  random bug |  login
Bug #11069 can't spawn new php after a few hours (mem leak?)
Submitted: 2001-05-23 18:32 UTC Modified: 2001-06-12 17:29 UTC
From: mike at kristopeit dot com Assigned:
Status: Not a bug Package: Apache related
PHP Version: 4.0.5 OS: win98
Private report: No CVE-ID: None
View Add Comment Developer Edit
Anyone can comment on a bug. Have a simpler test case? Does it work for you on a different platform? Let us know!
Just going to say 'Me too!'? Don't clutter the database with that please !
Your email address:
Solve the problem:
28 - 27 = ?
Subscribe to this entry?

 [2001-05-23 18:32 UTC] mike at kristopeit dot com
i run a web based game with a development server that gets around 100k hits a day.

after upgrading to apache 1.3.19 and php 4.0.5 and mysql 3.23.38 the server suddenly stops working and returns "internal server error" after a few hours, and apaches error.log reads "can't spawn child process"

i am using php as CGI now.  i used to use the module, but when i use the module now, the server works fine for about 10 minutes and then stops working completely (doesn't even return 500 internal server error)

these are the only 3 programs that are running and this didn't happen before i upgraded all the software.

i am using persistant connections on the db which i believe may be linked to the problem.


Add a Patch

Pull Requests

Add a Pull Request


AllCommentsChangesGit/SVN commitsRelated reports
 [2001-05-23 18:34 UTC]
No offense, but Win 98 is not really a stable server environment. I'd recommend a unix flavor, or at least Win2K for this job.

What software was you using before this upgrade?

 [2001-06-12 17:29 UTC]
No feedback, consider using something else as production
server OS than win98..

PHP Copyright © 2001-2024 The PHP Group
All rights reserved.
Last updated: Mon May 27 23:01:30 2024 UTC