|
php.net | support | documentation | report a bug | advanced search | search howto | statistics | random bug | login |
PatchesPull RequestsHistoryAllCommentsChangesGit/SVN commits
[2002-08-28 10:27 UTC] msisolak at yahoo dot com
[2002-08-28 12:33 UTC] kalowsky@php.net
[2003-01-18 16:09 UTC] phanto@php.net
[2003-01-18 16:09 UTC] phanto@php.net
[2003-01-29 20:06 UTC] phanto@php.net
|
|||||||||||||||||||||||||||||||||||||
Copyright © 2001-2025 The PHP GroupAll rights reserved. |
Last updated: Mon Oct 27 20:00:01 2025 UTC |
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();