#21775 [Fbk]: memory leak: emalloc(): Unable to alllocate 32 bytes

From: Date: Tue, 21 Jan 2003 15:36:56 +0000
Subject: #21775 [Fbk]: memory leak: emalloc(): Unable to alllocate 32 bytes
References: 1  Groups: php.bugs 
Request: Send a blank email to php-bugs+get-30835@lists.php.net to get a copy of this message
ID: 21775 Updated by: moriyoshi@php.net Reported By: peter.karl.mueller@gmx.de Status: Feedback Bug Type: Reproducible crash Operating System: SuSE Linux 7.3 PHP Version: 4.3.0 New Comment: The PHP scripting engine (ZendEngine) doesn't perform conservative GC, and any referenced object are marked as alive. Therefore there are some cases where the objects such as mutually-referenced ones remains undestroyed even though they are unreachable from the root set of variables. Your bi-directional linked list example is just one of such cases. Previous Comments: ------------------------------------------------------------------------ [2003-01-21 08:26:23] iliaa@php.net The memory limit option will not take effect unless you've compiled your PHP with --enable-memory-limit. ------------------------------------------------------------------------ [2003-01-21 07:26:32] moriyoshi@php.net Sorry, my bad. I missed "unset" statement. As for the memory-limit problem it was a bug indeed. See bug #20802. ------------------------------------------------------------------------ [2003-01-21 06:03:28] peter.karl.mueller@gmx.de 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] peter.karl.mueller@gmx.de PHP does not reclaim any memory no longer referenced? No garbage collection? ------------------------------------------------------------------------ [2003-01-20 11:12:37] moriyoshi@php.net 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. ------------------------------------------------------------------------ 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/21775 -- Edit this bug report at http://bugs.php.net/?id=21775&edit=1

« previous php.bugs (#30835) next »