#38591 [Bgs->Opn]: Memory Leak when using pathinfo and DirectoryIterator __toString

ID: 38591 User updated by: rr at d2g dot org dot uk Reported By: rr at d2g dot org dot uk -Status: Bogus +Status: Open Bug Type: *Directory/Filesystem functions Operating System: win XP PHP Version: 5.1.5 New Comment: I'm not 100% convinced that they are the same issue. I think this is related to the implementation of the magic method __toString. Mainly because if the line below, $tmp = pathinfo($file); is replaced with $tmp = pathinfo($file->__tostring()); The memory leak no longer seems present even though fundmentally these should be doing exactly the same thing. So I belive it is somthing to do with the implementation of the magic __toString() function. Previous Comments: ------------------------------------------------------------------------ [2006-08-29 12:09:04] tony2001@php.net Duplicate of bug #33487. ------------------------------------------------------------------------ [2006-08-29 12:04:57] rr at d2g dot org dot uk Every time the loop is executed the memory used by php increases by approx 4k. This happens even though everything is unset. So every loop the memory usage should return to the minimum amount but this doesn't happen the memory usage continues to increase. To view the error, load windows taskman and view the memory usage of php when running this code. You should see it slowly increasing. ------------------------------------------------------------------------ [2006-08-29 10:08:02] tony2001@php.net What do you mean by "memory leak" ? ------------------------------------------------------------------------ [2006-08-29 07:03:59] rr at d2g dot org dot uk Still present when using CSV snapshot. ------------------------------------------------------------------------ [2006-08-25 21:35:42] tony2001@php.net Please try using this CVS snapshot: http://snaps.php.net/php5.2-latest.tar.gz For Windows: http://snaps.php.net/win32/php5.2-win32-latest.zip ------------------------------------------------------------------------ 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/38591 -- Edit this bug report at http://bugs.php.net/?id=38591&edit=1