ID: 23331
Updated by: sniper@php.net
Reported By: jakub at icewarp dot com
-Status: Feedback
+Status: No Feedback
Bug Type: COM related
Operating System: W2K
PHP Version: 4.3.2RC1
New Comment:
No feedback was provided. The bug is being suspended because
we assume that you are no longer experiencing the problem.
If this is not the case and you are able to provide the
information that was requested earlier, please do so and
change the status of the bug back to "Open". Thank you.
Previous Comments:
------------------------------------------------------------------------
[2003-04-24 12:38:03] sniper@php.net
Please try using this CVS snapshot:
http://snaps.php.net/php4-STABLE-latest.tar.gz
For Windows:
http://snaps.php.net/win32/php4-win32-STABLE-latest.zip
------------------------------------------------------------------------
[2003-04-24 09:29:46] jakub at icewarp dot com
I have seen a few threads about Memory leaks in the COM object
implementation here but from what I see this has never been solved. For
instance this little piece of code proves it:
$excel=new COM("Excel.Application");
for ($i=0;$i<50000;$i++) $excel->sheetsinnewworkbook= "1";
die();
It's not always a property that causes the memory leak. It's also the
method you call when you pass strings to it. Also when you try to
reference a property that does not exist. I'm using my own COM object
to test it with and 5000 cycles o calling a simple 3 string parameter
function uses up to 30MB of RAM.
Please try to fix it. We have to use a CGI mode where every instance of
PHP is freed completely. But we want to use the ISAPI it is not
possible to do that now. Thank you
Jakub
------------------------------------------------------------------------
--
Edit this bug report at http://bugs.php.net/?id=23331&edit=1