#35820 [Fbk]: php4ts.dll memory leak

ID: 35820 Updated by: nlopess@php.net Reported By: ottawaremovethissixtyseven at hotmail dot com Status: Feedback Bug Type: IIS related Operating System: W2K PHP Version: 5CVS-2006-01-05 (snap) New Comment: I assume you are using the new IIS Debug Diagnostics Tool, so if you load the PHP debug symbols correctly you'll receive a more human-understandable report that you can send to us. I have not tried PHP4, but I don't get any error with PHP 5 (well I don't know which extensions you are using..) Previous Comments: ------------------------------------------------------------------------ [2006-01-07 17:11:50] sniper@php.net It's the thing that contains the function calls that called those functions that leaked. But try provide a reproducing script first. And not one with phpinfo(); which we know leaks. (it's meant to leak, no bug there) ------------------------------------------------------------------------ [2006-01-07 17:06:49] ottawaremovethissixtyseven at hotmail dot com What exactly is a calltrace? I will try and provide this. ------------------------------------------------------------------------ [2006-01-07 11:45:51] tony2001@php.net Nice try, but this info is totally useless without a calltrace. ------------------------------------------------------------------------ [2006-01-07 04:46:13] ottawaremovethissixtyseven at hotmail dot com Load Test: 5 hours. 300 concurrent users loading phpinfo(). DebugDiag results: php5ts.dll is responsible for 83.81 MBytes worth of outstanding allocations (69% Leak Probability). The following are the top 2 memory consuming functions: php5ts!_zend_hash_add_or_update+2da: 39.46 MBytes worth of outstanding allocations. php5ts!_zend_hash_add_or_update+15d: 23.05 MBytes worth of outstanding allocations. ------------------------------------------------------------------------ [2006-01-04 22:50:46] tony2001@php.net 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. ------------------------------------------------------------------------ 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