#21775 [Opn->Fbk]: memory leak: emalloc(): Unable to alllocate 32 bytes
| From: | iliaa@php.net | Date: | Tue, 21 Jan 2003 14:26:37 +0000 |
| Subject: | #21775 [Opn->Fbk]: memory leak: emalloc(): Unable to alllocate 32 bytes | ||
| References: | 1 | Groups: | php.bugs |
| Request: | Send a blank email to php-bugs+get-30828@lists.php.net to get a copy of this message | ||
ID: 21775
Updated by: iliaa@php.net
Reported By: peter.karl.mueller@gmx.de
-Status: Open
+Status: Feedback
Bug Type: Reproducible crash
Operating System: SuSE Linux 7.3
PHP Version: 4.3.0
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