Affected versions

• 82.0.1, 83.0b4

Affected platforms

• macOS 10.15;

Steps to reproduce

1. Launch Firefox, open the attached PDF file;
2. Press CTRL+P;
3. Save as PDF;
4. Open the Saved file in a new tab;

Expected result

• file content is open;

Actual result

• file open is empty;
• quick check on Chrome throws "File might be corrupted" error message;

Regression range

• pinpointing the regression range was difficult as; in some cases, a page refresh or waiting 10-ish seconds appeared to solve everything even on other 3rd party apps(Chrome).
• last good: 2020-09-11;
• first bad: 2020-09-12;
• Pushlog URL;

Additional notes

• S4 as suggested severity since out of 3 machines only 1 had this issue;
• checked with Downloading the file from the UI, there are no issues;
• flipping pdfjs.renderInteractiveForms on/off has no influence over it;
• 84.0a1 (2020-10-27) appears to be unaffected;
• considering the size of the file, waited a good 30seconds+ but still nothing.

Attaching the about:support content as well.

Could you attach to this bug the saved pdf which leads to "File might be corrupted" ?

Good point. Here is the resulted file.

If 84 is unaffected can you track down what fixed it?

Oddly enough, I couldn't reproduce the issue at all with either 83.0b4, 82.0.2, or the affected Nightly versions from when checking on mozregression(2020-09-12 and one from 2020-09-12).
Can only assume there was some race condition(?), or the fact that now my environment is "cleaner" as to why it doesn't reproduce.

The severity field is not set for this bug.
:bdahl, could you have a look please?

For more information, please visit auto_nag documentation.

I cannot reproduce the issue on windows 10 pro.
My feeling is that isn't an issue with pdf.js but who knows.
Anyway I close the bug as WFM, please reopen if you've a good way to reproduce it.