PHP Test results
| From: | noreply@php.net | Date: | Tue, 27 Aug 2002 21:07:23 +0000 |
| Subject: | PHP Test results | ||
| Groups: | php.qa | ||
| Request: | Send a blank email to php-qa+get-5900@lists.php.net to get a copy of this message | ||
array (
'user_name' => 'Michael Sisolak',
'email' => 'msisolak@yahoo.com',
'package' => '4.2.3RC1',
'testcase' => '0',
'status' => 'Good',
'os' => 'Windows NT/2K',
'sapi' => 'ISAPI',
'automake' => '1.4',
'autoconf' => '2.1.3',
'libtool' => '1.4.0',
'bison' => '1.2.8',
'com' => 'on',
'mssql' => 'on',
'test' => '',
'problems' => 'There appears to be a memory leak when setting a property value
of a
COM object in 4.2.3RC1. 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?
',
'bugids' => '',
'remarks' => '',
)