ID: 17606
Updated by: luimarma@iti.upv.es
Reported By: luimarma@iti.upv.es
-Status: Bogus
+Status: Closed
Bug Type: HTTP related
Operating System: RedHat 7.3
PHP Version: 4.2.1
New Comment:
Well, I have been doing more tests and it seems
that the system memory that is being used is for
the catching of the filesystem. I dont know if it
is a good thing that so many memory is eaten just
for file catching but this is an operating system
issue and not php related bug so If everyone
agrees I close the bug.
Regarding last message from Dreoth@houston.rr.com,
did you double check the values for the php.ini
file, related with post and file uploading?
Remenber that post limit should be at least
filesize+size of php script.
memory_limit = ??
post_max_size = ??
file_uploads = On
upload_max_filesize = ??
allow_url_fopen = On
Previous Comments:
------------------------------------------------------------------------
[2002-06-08 00:51:26] Dreoth@houston.rr.com
I'm using debian with a packaged release of 4.2.1
I'm having the same problem with large uploads, 12 MB files.
It will upload to the tmp directory, but fails to move it out of there
to where I desire. It eats system
memory as well. I've tried moving the uploaded file to a directory
(checked the permissions so on and so
forth) as well as moving the uploaded file into a mysql database as
binary information.
Nothing works. It uploads but wont do anything with it
------------------------------------------------------------------------
[2002-06-06 05:58:13] luimarma@iti.upv.es
Yes, I am using php-4.2.1, I have been doing
tests with very big files, my current parameters
regarding uploads in php.ini are the following:
memory_limit = 8M
post_max_size = 700M
file_uploads = On
upload_max_filesize = 700M
allow_url_fopen = On
When I try to upload a 400M file the web
server starts writing it in the tmp dir but it
also eats the system memory in the same amount so
it can only handle properly one big upload at a
time.
------------------------------------------------------------------------
[2002-06-06 05:58:08] luimarma@iti.upv.es
Yes, I am using php-4.2.1, I have been doing
tests with very big files, my current parameters
regarding uploads in php.ini are the following:
memory_limit = 8M
post_max_size = 700M
file_uploads = On
upload_max_filesize = 700M
allow_url_fopen = On
When I try to upload a 400M file the web
server starts writing it in the tmp dir but it
also eats the system memory in the same amount so
it can only handle properly one big upload at a
time.
------------------------------------------------------------------------
[2002-06-06 05:36:44] sesser@php.net
Are you sure you are using php 4.2.1 ?
Since php 4.2.0, uploaded files aren't stored in memory.
------------------------------------------------------------------------
[2002-06-06 05:27:20] luimarma@iti.upv.es
A more detailed study of the problem led me to
the next results.
Regardless de memory limit parameter the
file completelly uploads.
It writes the file to the temp dir at disk
as it loads the whole file into memory.
I can accept that this is a known behaviour but I
dont think that this is a good method if one is
willing to implement a php-web based software
repository. So the question is the following.
Is there any cons about just writting the file in
the tmp dir instead than duplicating the task
into memory?
Please, answer the question as I am evauating to
do the hack myself.
Thanks,
Luis
------------------------------------------------------------------------
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/17606
--
Edit this bug report at http://bugs.php.net/?id=17606&edit=1