ID:               35820
 Updated by:       [EMAIL PROTECTED]
 Reported By:      ottawaremovethissixtyseven at hotmail dot com
-Status:           Bogus
+Status:           Feedback
 Bug Type:         IIS related
 Operating System: W2K
 PHP Version:      5CVS-2006-01-03 (snap)
 New Comment:

Debug symbols:
http://snaps.php.net/win32/php5.1-dbgpack-win32-latest.zip

>There is a significant memory leak in php5ts.dll.
It's great that you keep repeating this and still have not provided any
information about the problem.
Does your debugger provide it?

Honestly saying, I don't think this leak even exists, because I can't
see any leaks with valgrind on Linux (and I'm sure nobody is able to
reproduce it on Windows) and I incline to think that your debugging
tool gives you wrong results.


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

[2006-01-04 22:46:39] [EMAIL PROTECTED]

Use the binaries provided at snaps.php.net and if you get some leak
with those -> reopen.

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

[2006-01-04 22:41:46] ottawaremovethissixtyseven at hotmail dot com

There is a significant memory leak in php5ts.dll. We are trying to
pinpoint it but do not have the debug symbols. We are have great
trouble compiling PHP 5.1.2RC2.

The memory leak is reproducible with this simple code:

<?php 
  phpinfo(); 
?> 

Can someone please point me in the right direction to get the debug
symbols for PHP 5.1.2RC2? We'll be able to provide detailed information
about what part of php5ts.dll is causing the memory leak if we can get
the debug symbols.

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

[2005-12-31 00:43:30] [EMAIL PROTECTED]

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



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

[2005-12-30 17:17:12] ottawaremovethissixtyseven at hotmail dot com

We're able to reproduce this memory leak by simply calling phpinfo()
during our performance test.

No DB API is used.

DebugDiag is showing a definite memory leak in php4ts.dll and the
XmlInitEncoding function even though we're only running this exact
code:

<?php 
  phpinfo(); 
?> 

We hit the server with over 300 concurrent users for several hours and
can reproduce the memory leak every time.

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

[2005-12-29 16:36:22] [EMAIL PROTECTED]

Is it necessary to use some DB API to reproduce a leak in XML-related
function?
And I should note that this script doesn't make any sense, since we
don't have the Connect.php and the database used, so we're unable just
run it and see the problem.

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

The remainder of the comments for this report are too long. To view
the rest of the comments, please view the bug report online at
    http://bugs.php.net/35820

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

Reply via email to