Bug #12316 Updated: Have to increase memory_limit to be able to upload big files

From: Date: Sun, 28 Oct 2001 22:35:03 +0000
Subject: Bug #12316 Updated: Have to increase memory_limit to be able to upload big files
References: 1  Groups: php.dev 
Request: Send a blank email to php-dev+get-69231@lists.php.net to get a copy of this message
ID: 12316 Updated by: sniper Reported By: jack@mobil.cz Old Status: Open Status: Closed Bug Type: Feature/Change Request Operating System: Linux PHP Version: 4.0.5 New Comment: This should be fixed in CVS now. You can try the latest snapshot from http://snaps.php.net/ Also, there are some minor leaks still in the new code. If you encounter such leaks, please send the shortest possible code + html with which you can reproduce the leak to php-dev@lists.php.net (or me) so we can get rid of these leaks. This fix will be in PHP 4.2.0. --Jani Previous Comments: ------------------------------------------------------------------------ [2001-07-23 09:01:30] jack@mobil.cz If you want to use file upload, you have to correctly set upload_max_size and post_max_size. That's o.k. But you also have to set memory_limit and max_execution_time to values high enough. The former seems to be result of very poor design (I admit I haven't checked the source code closely but as far as I can tell from a quick look at main/rfc1867.c, the whole form is first read and stored in memory and only then parsed and divided into files instead of being parsed on the run). I am not sure about the second issue since I don't know how exactly max_exec*_time works. Is it counted from the very start of request or from the moment script starts being executed? (that is -- if I set max_execution_time to 30 secs and the upload takes 55 secs, will PHP die? or will the upload finish and script will get 30secs to run?). I know I can get around this limit -- I just wonder. ------------------------------------------------------------------------ Edit this bug report at http://bugs.php.net/?id=12316&edit=1

« previous php.dev (#69231) next »