Thanks to all for the info here.  I'm a new member and not very technically savvy, but have already picked up so many tips from here.

I don't keep careful track of the large file issues because I don't use large files with my application.  But as far as I know the following is more or less correct:

1. This depends on your browser and how much of the html5 file handling portion of the standard it supports.  Older browsers and different brands of browser support different features in the standard.  I think that the latest versions of Chrome, Firefox at the least will only load each chunk into memory as they are needed.  But IE (for example) does not support any of the html5 file handling features - not even multiple file selection and upload so html5 does not work at all (much less chunking).

2. True for those browsers that need to load the whole file into memory, or if you are not using chunking, or you are using one of the other runtimes that needs to load the whole file into memory (for example flash).

3. See point number 1.  It depends on your brand and version of browser - I don't have a definitive answer.  There is automatic feature detection for html5 that you can look at once you have created and initialized your uploader.  I think it works relatively well and will tell you if chunking is supported.

There has only been a single insignificant change made to the master branch of plupload on github since the 1.5.1.1 release was made.  You can check the commits to see when the release notes were updated and check the minor change pushed in since then.

https://github.com/moxiecode/plupload/commits/

Hello,

The Vimeo uploader somehow handles w/o flash uploads up to 5GB w/o any kind of problems, and it does not seem to load the entire file into RAM.

After reading this thread it seems to accomplish the impossible

So any ideas how that uploader works?

Actually default Flash upload method (while having many other flaws), does this one right. So if you are not using resize option, chunking or custom headers, Plupload will fail back to default method, which doesn't load whole file in memory. Theoretically it can be any size, that your PC can handle.

I don't know if it will be any help but there is  a long thread regarding uploading to Amazon S3 here:

http://www.plupload.com/punbb/viewtopic.php?id=578

I have  tested Silverlight and Browserplus

Hi, i'm testing Plupload with large file because i would like to use it.
This is the config:

$(document).ready(function () {
    $("#uploader").pluploadQueue({
        runtimes: ('html5,silverlight'),
        url: 'Plupload/PluploadHandler.ashx',
        max_file_size: '10485760mb',
        chunk_size: '25mb',
        unique_names: false,
        flash_swf_url: 'Plupload/plupload.flash.swf',
        silverlight_xap_url: 'Plupload/plupload.silverlight.xap'
    });
});

HTML5 on Firefox works great (tested 5.5 GB file).

On IE9 with Silverlight, no problems with files < 2GB, but with files > 2GB, the progress remain at 0% and if i debug i get the following error in plupload.full.js when invoking
j().UploadFile(s[v.id], t.settings.url,.............

0x80004005 - Microsoft JScript runtime error: System.OverflowException: Value was either too large or too small for an Int32.

Can you please help me solve this problem?

I also tried to recompile jProgrammer branch on github ( https://github.com/JProgrammer/plupload … p/Plupload )
but it gives me the same error with files bigger than 2GB

0x80004005 - Microsoft JScript runtime error: System.OverflowException: Value was either too large or too small for an Int32.

Moreover i compared jProgrammer's "FileReference.cs" file with your last version one and seems like you implemented jProgrammer's inprovements changing Int32 into Long...but still gives me that Overflow error...

Ok Davit, thank you very much!

For now i solved changing

  up.settings.multipart_params = { fileSize: file.size, folderID: myId};

to

  up.settings.multipart_params = { fileSize: file.size.toString(), folderID: myId};

This avoid the cast in Int32!!!

I've been testing an implementation of this where users regularly upload 1GB+ files, and have been having problems with Flash and HTML5 uploading anything bigger then a 200MB file. Thanks