php.net |  support |  documentation |  report a bug |  advanced search |  search howto |  statistics |  random bug |  login

go to bug id or search bugs for

Bug #13408 Follow on to bug 7237: PHP ISAPI module leaks memory, crashes IIS
Submitted: 2001-09-23 16:09 UTC Modified: 2002-06-03 12:18 UTC
Votes:3
Avg. Score:4.3 ± 0.9
Reproduced:3 of 3 (100.0%)
Same Version:0 (0.0%)
Same OS:2 (66.7%)
From: john at userfrenzy dot com Assigned:
Status: Not a bug Package: IIS related
PHP Version: 4.0.6 OS: Win32
Private report: No CVE-ID: None
View Developer Edit
Welcome! If you don't have a Git account, you can't do anything here.
If you reported this bug, you can edit this bug over here.
(description)
Block user comment
Status: Assign to:
Package:
Bug Type:
Summary:
From: john at userfrenzy dot com
New email:
PHP Version: OS:

 

 [2001-09-23 16:09 UTC] john at userfrenzy dot com 
Apologies for submitting this under a new number: bug.php.net won't let me add this information to 7237 unless I have also entered a 'bug of my own' in order to register a password.  Please close this one straight away if necessary - I'll try to add this to 7237 right after this.

The problem is that the ISAPI module is leaking memory like a bastard.  I've just been monitoring Inetinfo.exe with the task manager running Squirrelmail, Geeklog and Phorum on 4 different sites.  Tested with IIS 4 (patched for all recent security and bug fixes) and PHP 4.0.6, btw.

Every page requested through the PHP interpreter via ISAPI causes the memory footprint of IIS to jump by upto 80k.  Holding down F5 (refresh) in my browser for 30 seconds will crash IIS in the way described above.

Using CGI instead is a workaround but unforunately because of bug 9802 (which is fixed in the ISAPI code), Squirrelmail (and several other apps) cannot function on IIS.

The bug, therefore, is related to memory management.

Patches

Pull Requests

History

AllCommentsChangesGit/SVN commitsRelated reports
 [2002-06-03 12:18 UTC] mfischer@php.net 
Thank you for taking the time to report a problem with PHP.
Unfortunately your version of PHP is too old -- the problem
might already be fixed. Please download a new PHP
version from http://www.php.net/downloads.php

If you are able to reproduce the bug with one of the latest
versions of PHP, please change the PHP version on this bug report
to the version you tested and change the status back to "Open".
Again, thank you for your continued support of PHP.
 
PHP Copyright © 2001-2024 The PHP Group
All rights reserved. 		Last updated: Sat Dec 21 16:01:28 2024 UTC