#36847 [Bgs->Opn]: debug_backtrace() result is not unset and eats memory
| From: | toggg@php.net | Date: | Sun, 26 Mar 2006 04:09:56 +0000 |
| Subject: | #36847 [Bgs->Opn]: debug_backtrace() result is not unset and eats memory | ||
| References: | 1 | Groups: | php.bugs |
| Request: | Send a blank email to php-bugs+get-94895@lists.php.net to get a copy of this message | ||
ID: 36847
User updated by: toggg@php.net
Reported By: toggg@php.net
-Status: Bogus
+Status: Open
Bug Type: Scripting Engine problem
Operating System: fc3
PHP Version: 5CVS-2006-03-24 (snap)
New Comment:
This not the same situation as #33487
Here, it's not a question of local variable within a method.
And we actually unset the created object.
If I do the same with $this->backtrace = str_pad(' ', 2300); then the
memory is not eaten up.
This occurs only if debug_backtrace() result is affected to a property
of the test object.
Previous Comments:
------------------------------------------------------------------------
[2006-03-26 01:03:57] tony2001@php.net
Duplicate of bug #33487.
------------------------------------------------------------------------
[2006-03-24 16:56:03] toggg@php.net
Description:
------------
It was originated by http://pear.php.net/bugs/bug.php?id=6788
Reproduce code:
---------------
<?php
class test
{
var $backtrace = null;
function test()
{
$this->backtrace = debug_backtrace();
}
}
set_time_limit(0);
for($i = 0; $i <= 10000; $i++) {
$ret = &new test();
unset($ret);
}
?>
Expected result:
----------------
nothing
Actual result:
--------------
memory exhausted
------------------------------------------------------------------------
--
Edit this bug report at http://bugs.php.net/?id=36847&edit=1