ID: 19342 Updated by: [EMAIL PROTECTED] Reported By: msisolak at yahoo dot com -Status: Duplicate +Status: Closed Bug Type: COM related Operating System: Windows 2000 PHP Version: 4.2.3 New Comment:
This bug has been fixed in CVS. In case this was a PHP problem, snapshots of the sources are packaged every three hours; this change will be in the next snapshot. You can grab the snapshot at http://snaps.php.net/. In case this was a documentation problem, the fix will show up soon at http://www.php.net/manual/. In case this was a PHP.net website problem, the change will show up on the PHP.net site and on the mirror sites in short time. Thank you for the report, and for helping us make PHP better. Previous Comments: ------------------------------------------------------------------------ [2002-10-02 07:19:02] [EMAIL PROTECTED] see 19150 ------------------------------------------------------------------------ [2002-09-10 13:35:44] msisolak at yahoo dot com There appears to be a memory leak when setting a property value of a COM object in 4.2.3. Running under ISAPI if this script is repeated memory usage continues to grow: $adodb = new COM("ADODB.Connection"); $adodb->ConnectionString = str_repeat("this is a text string!", 1000); Looking through the patches that have been applied, I believe that this is caused when COM.c went from 1.78 to 1.79 (which was then back-ported to 4.2.3). In this patch at the end of do_COM_propput(), this: FREE_VARIANT(new_value); became this: efree(new_value); // FREE_VARIANT does a VariantClear() which is not desired here ! If I reverse this patch I no longer see the leak and the code still appears to be working correctly. What was the purpose of this change? Does doing the FREE_VARIANT version cause some other issue? ------------------------------------------------------------------------ -- Edit this bug report at http://bugs.php.net/?id=19342&edit=1
