ID: 21775
Updated by: [EMAIL PROTECTED]
Reported By: [EMAIL PROTECTED]
Status: Open
Bug Type: Reproducible crash
Operating System: SuSE Linux 7.3
PHP Version: 4.3.0
New Comment:
Sorry, my bad. I missed "unset" statement.
As for the memory-limit problem it was a bug indeed. See bug #20802.
Previous Comments:
------------------------------------------------------------------------
[2003-01-21 06:03:28] [EMAIL PROTECTED]
my http process rund out of memory after it blowed up
to 320 MB (have 256 MB RAM). in php.ini memory_limit = 8M.
IMHO this is not bogus!
------------------------------------------------------------------------
[2003-01-20 11:38:05] [EMAIL PROTECTED]
PHP does not reclaim any memory no longer referenced?
No garbage collection?
------------------------------------------------------------------------
[2003-01-20 11:12:37] [EMAIL PROTECTED]
PHP is designed to bail out (to stop executing) when the memory has
been
run out. So it's natural that the runtime end up segfaulting.
------------------------------------------------------------------------
[2003-01-20 10:30:58] [EMAIL PROTECTED]
The following code:
<%
class Object {
var $prev;
var $next;
function unter (&$ref)
{
$ref->prev = &$this;
$this->next = &$ref;
}
};
while (true)
{
print "NEW ROUND\n";
{
$o = &new Object;
for ($i = 0; $i < 10000; ++$i) {
$o->unter (new Object);
$o = &$o->next;
}
unset ($o);
}
}
%>
consumes as much memory it can get. I would expect that
PHP garbage-collects the memory.
------------------------------------------------------------------------
--
Edit this bug report at http://bugs.php.net/?id=21775&edit=1
