#24015 [Opn->Csd]: DOMXML: xpath->free()

From: Date: Fri, 27 Aug 2004 08:22:29 +0000
Subject: #24015 [Opn->Csd]: DOMXML: xpath->free()
References: 1  Groups: php.bugs 
Request: Send a blank email to php-bugs+get-65333@lists.php.net to get a copy of this message
ID: 24015 Updated by: chregu@php.net Reported By: rbro at hotmail dot com -Status: Open +Status: Closed Bug Type: Feature/Change Request Operating System: RedHat 7.3 PHP Version: 4.3.2 New Comment: Thank you for your bug report. This issue has already been fixed in the latest released version of PHP, which you can download at http://www.php.net/downloads.php Previous Comments: ------------------------------------------------------------------------ [2003-06-04 23:10:33] sniper@php.net reclassified. ------------------------------------------------------------------------ [2003-06-04 11:56:53] rbro at hotmail dot com Where would I go to add a feature request? Also, do you have any short-term workarounds for this? I currently have a CLI script trying to process several thousand xml streams, and right now, it's using up all my RAM (512 MB) and all my virtual memory. Thanks. ------------------------------------------------------------------------ [2003-06-04 10:58:31] rrichards@php.net Currently you cant. You can add it as a feature request, but I cant say when or if it will be implemented. ------------------------------------------------------------------------ [2003-06-04 10:43:24] rbro at hotmail dot com Thanks for your reply - How do I free() the xpath object in the middle of my loop? I don't believe there is a xpath->free() function. ------------------------------------------------------------------------ [2003-06-04 10:30:04] rrichards@php.net As illustrated in your example, without the xpath context usage, memory uage remains constant. DomDocument->free will just free the document in memory. The memory increase you see is coming from the xpath objects you keep creating. ------------------------------------------------------------------------ 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/24015 -- Edit this bug report at http://bugs.php.net/?id=24015&edit=1

« previous php.bugs (#65333) next »