Bug #14053 Updated: Memory leak when using BIG array (>160MBytes)
ID: 14053
Updated by: sniper
Reported By: ingo.bez@in-systeme.de
Status: Feedback
Bug Type: Reproducible crash
Operating System: Linux (2.2.x/2.4.x)
PHP Version: 4.0.6
New Comment:
It would help also to know which database is this and
if you have some sort of short example script to add here
too.
Previous Comments:
------------------------------------------------------------------------
[2001-11-15 05:17:50] derick@php.net
How many elements are there in the array? And isn't there another way to do this?
Derick
------------------------------------------------------------------------
[2001-11-14 10:47:48] ingo.bez@in-systeme.de
We do query a database and put the fetched result into some array, whichs keys are the first field
of the fetched result-row. No problem to get the array build, it eats up about 180MBytes from the
2GBytes RAM the server has.
The script works fine, does some manipulation in the array (strings, ints) and re-inserts it into
the database.
After the script terminates - all output to the browser is done - the Apache-process responsible for
that request won't free the acquired memory. It instead eats one CPU completely for about
3-5minutes and then freezes - with aprox. 180MBytes of reserved RAM. (Fire the request 10 times and
be sure to have the swap working!)
We currently use:
- HP LC2000r (2*PIII 933MHz, 2GByte RAM, 18GB HDD)
- Linux (Slackware 8.0), glibc2.2.3, Kernel 2.4.13 SMP
- Apache 1.3.22
- PHP 4.0.6
- ZendOptimizer 1.1.0.
Tested and reproduced with:
- Apache 1.3.20, 1.3.17
- w/o ZendOptimizer.
- PHP4.2.0-dev
It'll be nice to hear from you!
Thanks in advance,
Ingo Bez
------------------------------------------------------------------------
Edit this bug report at http://bugs.php.net/?id=14053&edit=1
Thread (6 messages)