Bug #62444 [Com]: Handle leak in is_readable

From: Date: Wed, 25 Jul 2012 22:26:05 +0000
Subject: Bug #62444 [Com]: Handle leak in is_readable
References: 1  Groups: php.bugs 
Request: Send a blank email to php-bugs+get-172237@lists.php.net to get a copy of this message
Edit report at https://bugs.php.net/bug.php?id=62444&edit=1

 ID:                 62444
 Comment by:         smiles_indonesia at yahoo dot co dot id
 Reported by:        sergio dot nalin at gmail dot com
 Summary:            Handle leak in is_readable
 Status:             Open
 Type:               Bug
 Package:            Filesystem function related
 Operating System:   Win 7 64bit
 PHP Version:        5.3.14
 Block user comment: N
 Private report:     N

 New Comment:

It seems happened since introduction of php 5.3.0. If you see in the changelogs:

http://www.php.net/ChangeLog-5.php

Added support for ACL (is_writable, is_readable, reports now correct results) on Windows. (Pierre,
Venkat Raman Don, Kanwaljeet Singla)

This issue is very critical, because it makes php running on windows production server impractical /
unusable...

My quad xeon box becomes very slow after some days, the ram usage is mysteriously increased (httpd
process usage still remains the same, I thought handle consumes kernel spaces)...

If your webserver servers 1 million request, then there will be about 1 million handle opened...
Usual application only consumes 20 to 2000 handles...


Previous Comments:
------------------------------------------------------------------------
[2012-06-29 00:10:17] sergio dot nalin at gmail dot com

Description:
------------
PHP vc9 5.3.14, thread safe version + Apache Httpd 2.2.22 + Win 7/Win Server 2008 
R2

Each time is_readable in invoked, it leaves an open handle in the httpd process.



Test script:
---------------
for($i=0; $i<100;$i++) {
  is_readable("c:\\temp");
}

NOTE: the folder/file must exist for the leak to happen.

Expected result:
----------------
No leaked handles

Actual result:
--------------
100 leaked handles


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



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


Thread (8 messages)

« previous php.bugs (#172237) next »