I'm working on a cms tool on a suse7/apache/mysql system. Usually I get very few entries in the error log for this tool, so I think I did not such a bad job... but recently I got a quite a few memory overflow msgs. Both in the error log and during script execution. I guess that it has something to do with the upload of binary files through a modified version of Florian Dittmer's upload script (available from phpbuilder), 'cause the problem starts usually after uploading a file. But I can hardly reproduce the error willingly.
Is there a way to make sure that all unneeded memory is cleaned up after script execution? I think the php memory manager does not such a good job...
I tried to cut down memory usage with mysql_free_result, but it did not really help. >>From the documentation: mysql_free_result() only needs to be called if you are concerned about how much memory is being used for queries that return large result sets. All associated result memory is automatically freed at the end of the script's execution.<<
I still use PHP 4.0.4pl1, maybe it would help to update to PHP 4.0.6. Any experience?
Is there a way to make sure that all unneeded memory is cleaned up after script execution? I think the php memory manager does not such a good job...
I tried to cut down memory usage with mysql_free_result, but it did not really help. >>From the documentation: mysql_free_result() only needs to be called if you are concerned about how much memory is being used for queries that return large result sets. All associated result memory is automatically freed at the end of the script's execution.<<
I still use PHP 4.0.4pl1, maybe it would help to update to PHP 4.0.6. Any experience?