#35820 [Opn->Fbk]: php4ts.dll memory leak
ID: 35820 Updated by: [EMAIL PROTECTED] Reported By: ottawaremovethissixtyseven at hotmail dot com -Status: Open +Status: Feedback Bug Type: IIS related Operating System: W2K PHP Version: 5CVS-2006-01-05 (snap) New Comment: 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 You can find the debug pack here for it: http://snaps.php.net/ Previous Comments: [2006-01-11 19:18:05] ottawaremovethissixtyseven at hotmail dot com Yes. We are using IIS Debug Diagnostics Tool. We will send a human readable report shortly. Can you please tell me where I can find the debug symbols for the PHP 5.1.1 official November 28th release? [2006-01-08 13:22:05] [EMAIL PROTECTED] 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..) [2006-01-07 17:11:50] [EMAIL PROTECTED] 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] [EMAIL PROTECTED] Nice try, but this info is totally useless without a calltrace. 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
#35820 [Opn->Fbk]: php4ts.dll memory leak
ID: 35820 Updated by: [EMAIL PROTECTED] Reported By: ottawaremovethissixtyseven at hotmail dot com -Status: Open +Status: Feedback Bug Type: IIS related Operating System: W2K PHP Version: 5CVS-2006-01-05 (snap) New Comment: 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) Previous Comments: [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] [EMAIL PROTECTED] 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] [EMAIL PROTECTED] 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. [2005-12-27 19:28:43] ottawaremovethissixtyseven at hotmail dot com Description: Latest 4.x snapshot has memory leaks in php4ts.dll. Here is the output from the debugger: --- php4ts.dll is responsible for 45.47 MBytes worth of outstanding allocations (92% Leak Probability). The following are the top 2 memory consuming functions: php4ts!XmlParseXmlDecl+9d: 21.43 MBytes worth of outstanding allocations. php4ts!XmlParseXmlDecl+fb: 13.86 MBytes worth of outstanding allocations. --- We are running performance tests against W2K/IIS5 in ISAPI mode. Very simple PHP scripts which open a connection to Oracle thru ODBC. These performance test run without issue in CGI mode but the CPU performance is unacceptable so we are trying to get ISAPI working. -- Edit this bug report at http://bugs.php.net/?id=35820&edit=1
#35820 [Opn->Fbk]: php4ts.dll memory leak
ID: 35820 Updated by: [EMAIL PROTECTED] Reported By: ottawaremovethissixtyseven at hotmail dot com -Status: Open +Status: Feedback Bug Type: IIS related Operating System: W2K PHP Version: 4CVS-2005-12-27 (snap) New Comment: 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 Previous Comments: [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: 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. [2005-12-29 16:29:14] ottawaremovethissixtyseven at hotmail dot com As part of troubleshooting we created this simple PHP script and ran an intense performance test: Our debugger is showing: a 97% leak probability in php4ts!XmlInitEncoding Please let me know if you need additional information. [2005-12-27 20:51:55] [EMAIL PROTECTED] Short reproducable scripts are fine. Please leave the status at "feedback" until you can provide those. [2005-12-27 20:38:56] ottawaremovethissixtyseven at hotmail dot com I'm guessing you're looking for the PHP scripts that are being used in this performance test. I'm working on getting this. If you need anything other than the scripts please let me know. 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
#35820 [Opn->Fbk]: php4ts.dll memory leak
ID: 35820 Updated by: [EMAIL PROTECTED] Reported By: ottawaremovethissixtyseven at hotmail dot com -Status: Open +Status: Feedback Bug Type: IIS related Operating System: W2K PHP Version: 4CVS-2005-12-27 (snap) New Comment: 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. Previous Comments: [2005-12-29 16:29:14] ottawaremovethissixtyseven at hotmail dot com As part of troubleshooting we created this simple PHP script and ran an intense performance test: Our debugger is showing: a 97% leak probability in php4ts!XmlInitEncoding Please let me know if you need additional information. [2005-12-27 20:51:55] [EMAIL PROTECTED] Short reproducable scripts are fine. Please leave the status at "feedback" until you can provide those. [2005-12-27 20:38:56] ottawaremovethissixtyseven at hotmail dot com I'm guessing you're looking for the PHP scripts that are being used in this performance test. I'm working on getting this. If you need anything other than the scripts please let me know. [2005-12-27 20:04:12] [EMAIL PROTECTED] It's possible if you provide some more information about the issue. The patch would be good too. [2005-12-27 20:01:09] ottawaremovethissixtyseven at hotmail dot com We are currently unable to use PHP 5 with our application. Any chance this memory leak will be fixed in an upcoming PHP 4.x snapshot? 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
#35820 [Opn->Fbk]: php4ts.dll memory leak
ID: 35820 Updated by: [EMAIL PROTECTED] Reported By: ottawaremovethissixtyseven at hotmail dot com -Status: Open +Status: Feedback Bug Type: IIS related Operating System: W2K PHP Version: 4CVS-2005-12-27 (snap) New Comment: Short reproducable scripts are fine. Please leave the status at "feedback" until you can provide those. Previous Comments: [2005-12-27 20:38:56] ottawaremovethissixtyseven at hotmail dot com I'm guessing you're looking for the PHP scripts that are being used in this performance test. I'm working on getting this. If you need anything other than the scripts please let me know. [2005-12-27 20:04:12] [EMAIL PROTECTED] It's possible if you provide some more information about the issue. The patch would be good too. [2005-12-27 20:01:09] ottawaremovethissixtyseven at hotmail dot com We are currently unable to use PHP 5 with our application. Any chance this memory leak will be fixed in an upcoming PHP 4.x snapshot? [2005-12-27 19:41:05] [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-27 19:28:43] ottawaremovethissixtyseven at hotmail dot com Description: Latest 4.x snapshot has memory leaks in php4ts.dll. Here is the output from the debugger: --- php4ts.dll is responsible for 45.47 MBytes worth of outstanding allocations (92% Leak Probability). The following are the top 2 memory consuming functions: php4ts!XmlParseXmlDecl+9d: 21.43 MBytes worth of outstanding allocations. php4ts!XmlParseXmlDecl+fb: 13.86 MBytes worth of outstanding allocations. --- We are running performance tests against W2K/IIS5 in ISAPI mode. Very simple PHP scripts which open a connection to Oracle thru ODBC. These performance test run without issue in CGI mode but the CPU performance is unacceptable so we are trying to get ISAPI working. -- Edit this bug report at http://bugs.php.net/?id=35820&edit=1
#35820 [Opn->Fbk]: php4ts.dll memory leak
ID: 35820 Updated by: [EMAIL PROTECTED] Reported By: ottawaremovethissixtyseven at hotmail dot com -Status: Open +Status: Feedback Bug Type: IIS related Operating System: W2K PHP Version: 4CVS-2005-12-27 (snap) New Comment: It's possible if you provide some more information about the issue. The patch would be good too. Previous Comments: [2005-12-27 20:01:09] ottawaremovethissixtyseven at hotmail dot com We are currently unable to use PHP 5 with our application. Any chance this memory leak will be fixed in an upcoming PHP 4.x snapshot? [2005-12-27 19:41:05] [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-27 19:28:43] ottawaremovethissixtyseven at hotmail dot com Description: Latest 4.x snapshot has memory leaks in php4ts.dll. Here is the output from the debugger: --- php4ts.dll is responsible for 45.47 MBytes worth of outstanding allocations (92% Leak Probability). The following are the top 2 memory consuming functions: php4ts!XmlParseXmlDecl+9d: 21.43 MBytes worth of outstanding allocations. php4ts!XmlParseXmlDecl+fb: 13.86 MBytes worth of outstanding allocations. --- We are running performance tests against W2K/IIS5 in ISAPI mode. Very simple PHP scripts which open a connection to Oracle thru ODBC. These performance test run without issue in CGI mode but the CPU performance is unacceptable so we are trying to get ISAPI working. -- Edit this bug report at http://bugs.php.net/?id=35820&edit=1
#35820 [Opn->Fbk]: php4ts.dll memory leak
ID: 35820 Updated by: [EMAIL PROTECTED] Reported By: ottawaremovethissixtyseven at hotmail dot com -Status: Open +Status: Feedback Bug Type: IIS related Operating System: W2K PHP Version: 4CVS-2005-12-27 (snap) New Comment: 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 Previous Comments: [2005-12-27 19:28:43] ottawaremovethissixtyseven at hotmail dot com Description: Latest 4.x snapshot has memory leaks in php4ts.dll. Here is the output from the debugger: --- php4ts.dll is responsible for 45.47 MBytes worth of outstanding allocations (92% Leak Probability). The following are the top 2 memory consuming functions: php4ts!XmlParseXmlDecl+9d: 21.43 MBytes worth of outstanding allocations. php4ts!XmlParseXmlDecl+fb: 13.86 MBytes worth of outstanding allocations. --- We are running performance tests against W2K/IIS5 in ISAPI mode. Very simple PHP scripts which open a connection to Oracle thru ODBC. These performance test run without issue in CGI mode but the CPU performance is unacceptable so we are trying to get ISAPI working. -- Edit this bug report at http://bugs.php.net/?id=35820&edit=1
