uploading eats all memory

Status: Alpha

Brought to you by: braga

#4 uploading eats all memory

Status: open

Owner: Robson Braga Araujo

Labels: None

Priority: 5

Updated: 2006-06-17

Created: 2006-06-03

Creator: Radek Podgorny

Private: No

The current practice of uploading is quite insane. For
each write() you just inflate a buffer and do the real
upload on flush(). Try uploading a large file and it
will kill you machine for sure...

Discussion

Robson Braga Araujo - 2006-06-17

Logged In: YES
user_id=307089

I'm aware of the problem. I'll address this in a future version.

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Robson Braga Araujo - 2006-06-17

assigned_to: nobody --> braga
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Casper Langemeijer - 2006-10-17

Logged In: YES
user_id=1053109

Could you give an idea as to when you have the time to fix this?

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Jeff McGlynn - 2006-11-02

Logged In: YES
user_id=1513774

This just happened to me, and it sent my load averages to 50 in the process.

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Nobody/Anonymous - 2007-03-23

Logged In: NO

jepp,

using it for backup tars to another server and it occupies 900+ MB RAM, thats not good

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Nobody/Anonymous - 2007-03-23

Logged In: NO

PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
14092 root 16 0 1970m 1.2g 1028 S 2.0 63.6 0:24.24 curlftpfs

and its not even released when canceling!!!!

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Gunter Ohrner - 2007-05-03

Logged In: YES
user_id=290799
Originator: NO

Uhm, I also just ran into this problem with the Debian package of curlftpfs - uploading a tar which exceeds one GB in size just kills curlftpfs, althought sufficient memory should still have been available.
However, using 1 GB RAM for uploading a file is no option for me in any case, is there any way to fix this or work around this problem, or will I have to switch away from curlftpfs, to another file upload solution?

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Nobody/Anonymous - 2007-06-30

Logged In: NO

please define "future" ...

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Nobody/Anonymous - 2007-10-29

Logged In: NO

Hello braga,

as a happy user of curlftpfs I want to thank you for your time.
But, as others have pointed out, the current practice of uploading files makes it unusable for many of us.
Is there anything I can do to help you fix that? Unfortunately, coding in C is not in my skillset.

Best regards

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Nobody/Anonymous - 2008-04-06

Logged In: NO

Confirmed,
curlftpfs is unusable for uploading large files, it tries to cache the entire file into RAM, then crashes.

This has been reported 2 years ago, so maybe it's not possible to fix it ?
Will it be fixed soon ? if not when will it be fixed ? do you need someone to fix it for you ?
I saw that there are no news since one year now, is this project dead ?

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Alexandre Ahmim-Richard - 2008-05-21

Logged In: YES
user_id=1296790
Originator: NO

will this issue be fixed someday ? Still open for 2 years and seems to me as a major one because it brokes the upload of large files.

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Log in to post a comment.