Saving large files save as zero byte files
Categories
(MailNews Core :: Backend, defect)
Tracking
(Not tracked)
People
(Reporter: musor, Unassigned)
Details
Attachments
(1 file)
30.43 KB,
image/png
|
Details |
User Agent: Mozilla/5.0 (Windows NT 6.1; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/86.0.4240.198 Safari/537.36
Steps to reproduce:
Mail synchronization is disabled in the account settings.
I receive an attachment of more than 20MB.
I click "save all" attachments to the folder.
Actual results:
Files with zero size are saved.
The message is successfully forwarded to another mailbox, and is displayed in the sent ones. But it is not possible to download the attachment.
The only way to download a package is to first save the email as an eml file. Then "save everything" works correctly.
Expected results:
ll files attached to the letter.
Comment 1•4 years ago
|
||
Files with zero size are saved.
Where? On a local filesystem? On some remote file system?
Comment hidden (duplicate) |
(In reply to Andre Klapper from comment #1)
Files with zero size are saved.
Where? On a local filesystem? On some remote file system?
Local and remote.
Tested on two PCs. With a clean profile.
There is no problem in another program.
Comment 4•3 years ago
|
||
TCW can you reproduce? (note mail sync is disabled per comment 0)
Comment 5•3 years ago
|
||
(In reply to Wayne Mery (:wsmwk) from comment #4)
TCW can you reproduce? (note mail sync is disabled per comment 0)
Using 86.0b3 and testing with a 21MB wav file. When I disabled Mail Sync on one account and sent it to that one account, Save As downloads / saves a 27 byte file (reporting 0 bytes in disk). So, looks like this is a valid bug per STR. Oddly, nothing in Error Console.
Flipping Mail Sync back on and then restarting TB does download the full file at its actual size.
Comment 6•3 years ago
|
||
related to bug 1673093 ?
Comment 7•3 years ago
|
||
fwiw I couldn't reproduce with a smaller file of 1.2mb
Updated•3 years ago
|
Comment 10•3 years ago
|
||
regression?
Maybe could be considered a regression of turning off fetch on demand for crypto, not sure.
Not a simple problems for describe or to fix, but I do described some possible work-arounds in the duplicate bug 1673093.
Description
•