ID: 19150
Updated by: [EMAIL PROTECTED]
Reported By: [EMAIL PROTECTED]
-Status: Open
+Status: Suspended
Bug Type: COM related
Operating System: Windows 2000
PHP Version: 4.2.2, 4.3.0-dev
New Comment:
suspending
Previous Comments:
------------------------------------------------------------------------
[2003-01-18 16:09:20] [EMAIL PROTECTED]
heading for php5 i won't spend any more time on fixing memleaks in php4
code
------------------------------------------------------------------------
[2002-08-28 12:33:50] [EMAIL PROTECTED]
updating version
------------------------------------------------------------------------
[2002-08-28 10:27:20] [EMAIL PROTECTED]
I did confirm that the bug exists in the current HEAD branch, but was
unable to confirm the fix as the com_invoke call would fail.
------------------------------------------------------------------------
[2002-08-28 10:25:41] [EMAIL PROTECTED]
If a COM property set is called on an overloaded object that was
created by a COM method call, memory leaks (as identified by an ever
growing DLLHOST memory size under the ISAPI filter). This does not
happen if you use the functional COM interface.
This will leak:
$xml = new COM("MSXML.DOMDocument");
$element = $xml->createElement("test");
$element->text = str_repeat("this is a text string!", 100);
$element->Release();
$xml->Release();
but this doesn't:
$xml = new COM("MSXML.DOMDocument");
$element = com_invoke($xml, "createElement", "test");
com_set($element, "text", str_repeat("this is a text string!", 100));
com_release($element);
$xml->Release();
------------------------------------------------------------------------
--
Edit this bug report at http://bugs.php.net/?id=19150&edit=1
