1597238 - Filelink webextensions seem to fail when attachment is bigger than 250Mb

Status: RESOLVED WORKSFORME

(Thunderbird :: FileLink, defect)

Description

[na_th_an]

Attachment: 268M.png

User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/78.0.3904.97 Safari/537.36

Steps to reproduce:

I'm in the process of rewriting an old Filelink plugin as a webextension. My code is based on the Dropbox Filelink plugin.

This happens when I try to upload a file which is bigger than 250 with both my extension and the unmodified Dropbox Filelink extension.

Actual results:

Everything works fine when the file is less than around 250Mb. But if the file is bigger than 250Mb, the browser.cloudFile.onFileUpload listener is not fired, the upload fails (with the "the file could not be uploaded" message box), and the console logs this error:

WebExtensions:
Exception { name: "NS_ERROR_FAILURE", message: "", result: 2147500037, filename: "resource://gre/modules/MessageChannel.jsm", lineNumber: 369, columnNumber: 0, data: null, stack: "sendMessage@resource://gre/modules/MessageChannel.jsm:369:27\nsendMessage@resource://gre/modules/MessageChannel.jsm:883:14\nsendMessage@resource://gre/modules/ExtensionCommon.jsm:662:27\nlistener@resource://gre/modules/ExtensionParent.jsm:1183:10\napplySafeWithoutClone@resource://gre/modules/ExtensionCommon.jsm:588:24\napplySafe@resource://gre/modules/ExtensionParent.jsm:784:17\naddListener/async/<@resource://gre/modules/ExtensionCommon.jsm:2387:33\n", location: XPCWrappedNative_NoHelper }
ext-cloudFile.js:129

Expected results:

The browser.cloudFile.onFileUpload listener should have been fired and the file should have been correctly uploaded.

I've tried to add a console.log command at the top of my listener and the message never appears so I guess the listener code is not being executed at all. The error happens before.

browser.cloudFile.onFileUpload.addListener(async (account, { id, name, data }) => {
console.log ("Attempting to upload " + name);
...
etc

This happens exactly the same with the Dropbox Filelink extension.

Is 250Mb the limit?

Comment 1

[Geoff Lankow (:darktrojan)]

It may well be a limit I was not aware of. However, I changed my test extension to use File objects instead of ArrayBuffer objects, and that appeared to work. (See the docs for how to do that.)

Comment 2

[na_th_an]

I will check that out. Many thanks.

Comment 3

[Wayne Mery (:wsmwk)]

(In reply to na_th_an from comment #2)

I will check that out. Many thanks.

results?

Comment 4

[na_th_an]

It works for files > 250Mb using File objects instead of ArrayBuffer objects, as sugested.

Comment 5

[laksdfölkj]

Hi

It seems, it relates also me as a "standad" user (TB 68.3.1 32bit on W10).
151MB works
227MB works
379MB does not work.
When can we expect this bug is fixed in the "release" channel?

Thanks
Ralf

Comment 6

[carterbrandon]

I also experience this behaviour consistently, using WeTransfer via FileLink on this environment:

Windows 10 Home (1909)
Thunderbird 68.10.0 (32 bit)

Comment 7

[Geoff Lankow (:darktrojan)]

It's true that the WeTransfer provider hasn't been updated with the settings I mentioned in comment 1. I just filed bug 1650680 to do that.

Meanwhile this bug has a solution, so I'm closing it.