Open
Bug 1398540
Opened 7 years ago
Updated 2 years ago
Printing Experian report to PDF is very slow and text becomes images in the output PDF
Categories
(Core :: Printing: Output, defect, P3)
Tracking
()
NEW
People
(Reporter: jchen, Unassigned)
References
()
Details
(Keywords: regression, reproducible)
Trying to print an Experian credit report to a PDF file using CutePDF Writer, Nightly would hang in intervals while using large amounts of memory. The final printed PDF file also consists of large images, making the text on the page not selectable in a PDF viewer. I saved a sanitized version of the report at [1]. Using that, I can reproduce the same behavior on two Windows 10 machines, using CutePDF, Foxit, and Microsoft PDF printers. mozregression traces the regression to bug 1361787. For comparison, prior to that bug, the test page prints in seconds, while after the bug, the same page prints in minutes while causing hangs in-between. [1] https://moz.jnchen.com/tests/experian-sanitized.html Mason, can you take a look since you worked on bug 1361787?
Flags: needinfo?(mchang)
Comment 1•7 years ago
|
||
(In reply to Jim Chen [:jchen] [:darchons] from comment #0) > Trying to print an Experian credit report to a PDF file using CutePDF > Writer, Nightly would hang in intervals while using large amounts of memory. > The final printed PDF file also consists of large images, making the text on > the page not selectable in a PDF viewer. > > I saved a sanitized version of the report at [1]. Using that, I can > reproduce the same behavior on two Windows 10 machines, using CutePDF, > Foxit, and Microsoft PDF printers. mozregression traces the regression to > bug 1361787. For comparison, prior to that bug, the test page prints in > seconds, while after the bug, the same page prints in minutes while causing > hangs in-between. > > [1] https://moz.jnchen.com/tests/experian-sanitized.html > > Mason, can you take a look since you worked on bug 1361787? What do you mean by you can reproduce the same behavior on windows 10 machines with CutePDF and Foxit?
Flags: needinfo?(mchang) → needinfo?(nchen)
Reporter | ||
Comment 2•7 years ago
|
||
CutePDF and Foxit are two other PDF printers that I tried, to see if it's likely an issue in Firefox, rather than an issue in a particular printer driver.
Flags: needinfo?(nchen)
Updated•7 years ago
|
Priority: -- → P3
Comment 3•7 years ago
|
||
(In reply to Jim Chen [:jchen] [:darchons] from comment #2) > CutePDF and Foxit are two other PDF printers that I tried, to see if it's > likely an issue in Firefox, rather than an issue in a particular printer > driver. I don't understand. So you mean that with CutePDF and Foxit, you can reproduce the slow printing? From this bug, this is just a long standing regression. We sped up box shadows and found some issues with printing when using the 9 box shadow border approach. Bug 1361787 just put us back to how we were rendering box shadows while printing to pre bug 1155828, which was Gecko 41.
Flags: needinfo?(nchen)
Reporter | ||
Comment 4•7 years ago
|
||
(In reply to Mason Chang [:mchang] from comment #3) > (In reply to Jim Chen [:jchen] [:darchons] from comment #2) > > CutePDF and Foxit are two other PDF printers that I tried, to see if it's > > likely an issue in Firefox, rather than an issue in a particular printer > > driver. > > I don't understand. So you mean that with CutePDF and Foxit, you can > reproduce the slow printing? Correct, printing the test case to PDF is slow via any of the PDF printers I tried. I tried the test case with a Nightly build from a few days before bug 1155828 landed, and it seemed to be fine. The old build is a lot faster than right now, and the output retained all the text, instead of converting all the text to images.
Flags: needinfo?(nchen)
Updated•7 years ago
|
status-firefox57:
--- → wontfix
status-firefox58:
--- → fix-optional
Comment 5•6 years ago
|
||
https://wiki.mozilla.org/Bug_Triage/Projects/Bug_Handling/Bug_Husbandry#Move_fix-optionals
status-firefox59:
--- → ?
Updated•2 years ago
|
Severity: normal → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•