When trying to upload a large file using [Reactive Multiple File Upload] I experience following behaviour:
Firefox: when uploading a file larger than approximately 800MB (say 850MB) event OnFileUpload is NOT triggered.
Chrome/Edge: when uploading a file larger than approximetely 400MB (say 450MB) event OnFileUpload is triggered but the content of variable inpFileBinaryData is NullBinary() even though variable inpFileSize contains the correct file size.
So there is a limit in file size that I can upload which depends on the Browser.For Chrome/Edge I can handle that by comparing the calculated binary size with the actual file size provided by inpFileSize and inform the user that the file is to large. But for Firefox this does not work as event OnFileUpload is not triggered at all.
Event OnFileUploadError is not triggered in both cases.
Does anybody have any suggestions what I can do in this situation? In our company Firefox is the default browser, so I cannot simply switch to Chrome/Edge.
If you need further information, please let me know.
Best regards,
Paul
I haven't verified this against the asset's code, so take it as a hint rather than a confirmed cause. The asset reads the selected file into memory in the browser to build the binary, and browsers have limits on how much a single file read/string can hold (Chrome and Edge tend to fail somewhere around a few hundred MB, Firefox a bit later), which would match what you're seeing, including the size being correct while the binary is empty. For files this large, a chunked upload straight to a REST endpoint (or a resumable-upload approach) is usually safer than reading the whole file into a Binary Data variable on the client.
Thanks for your quick reply. I assume you are right about the memory limit. Still I would expect some type of error handling in this case.
Regarding your suggestion: how would you read in the file in the first place?
Agreed, a proper error event would be a better experience. @José Pedro Proença , could you take a look? It would help if the asset raised OnFileUploadError when the file can't be read, instead of failing silently.
To answer your question: you'd skip reading the whole file into one Binary Data variable. With a JavaScript node you can take the File from the input and slice it into chunks (File.slice), then send each chunk with fetch/XHR to an exposed REST endpoint, and reassemble the pieces on the server side. Since slice() doesn't load the whole file into memory, the size limit stops being a browser-memory problem. I haven't tested this with the Reactive Multiple File Upload asset itself, so treat it as a general approach rather than a tested recipe.