ID: 41675 Updated by: [EMAIL PROTECTED] Reported By: wiggum24 at gmail dot com -Status: Open +Status: Feedback Bug Type: Performance problem Operating System: Redhat Enterprise Linux 4 PHP Version: 5.2.3 New Comment:
Thank you for this bug report. To properly diagnose the problem, we need a short but complete example script to be able to reproduce this bug ourselves. A proper reproducing script starts with <?php and ends with ?>, is max. 10-20 lines long and does not require any external resources such as databases, etc. If the script requires a database to demonstrate the issue, please make sure it creates all necessary tables, stored procedures etc. Please avoid embedding huge scripts into the report. Previous Comments: ------------------------------------------------------------------------ [2007-06-13 00:34:35] wiggum24 at gmail dot com Description: ------------ Since upgrading from 5.1.? to 5.2.3, we're having problems with memory limits being exhausted, we never encountered this problem previously. Our memory_limit on all production servers was set to 8 meg and we never had a problem, after this upgrade I've knocked it up to 64 meg and we're still having problems with some scripts. Some instances give "memory limit exhausted", the scripts just stops without generating an error in other instances. Error is reproducable, the same scripts stop consistently. Pulling a large recordset out of a database is usually the culprit, but it happens with both MS SQL server and Postgres. I've done a bit of googling, other people are experiencing this inflated memory requirement problem. Reproduce code: --------------- $sql="SELECT * FROM blah WHERE foo=1"; $rs=$db->query($sql); Expected result: ---------------- For it to return my recordset :) Actual result: -------------- Either: - script stops mid execution without error - generates "memory limit exhausted" error ------------------------------------------------------------------------ -- Edit this bug report at http://bugs.php.net/?id=41675&edit=1
