924072 - PDF file making Firefox unresponsive

Status: UNCONFIRMED

(Firefox :: PDF Viewer, defect, P3)

Description

[Martin Mitáš]

User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:24.0) Gecko/20100101 Firefox/24.0 (Beta/Release)
Build ID: 20130910160258

Steps to reproduce:

1. Go to http://securityspread.com/S0urce/LatestDetectionRates.pdf (using the built-in pdf.js viewer)
2. Use zoom (200%).

(Firefox version 24 on MacOS X 10.8.5)



Actual results:

Firefox became unresponsive (even switching to other tab, quitting, etc. did not work), the system was extremely busy, however I could not analyze due time constrains. 

Even killing Firefox was problematic due to the mouse event (opening terminal) and keyboard lags.


Expected results:

Just render the document, or at least report an error instead of freezing the computer.

Comment 1

[Loic]

Same on Win 7, it's a huge PDF (not in size, but in details). At each new zoom-in level, the memory use increases.

Comment 2

[Brendan Dahl [:bdahl]]

Performance issue is mainly with the text layer used for text selection.  Works fine with http://securityspread.com/S0urce/LatestDetectionRates.pdf#textLayer=off

Comment 3

[Nicholas Nethercote [inactive]]

That PDF is a real stress test.

On my Linux box:

- A dev version of plf.js took 45 seconds to show the content, and then some more time to generate the text layer. Scrolling performance was terrible. After disabling the text layer, scrolling performance was fine.

- evince failed to display anything and I gave up trying after 3 minutes.

- On Mac, Preview took a mere 3 seconds to render.

pdf.js's text layer has 42,000 text divs! No wonder the scrolling is slow.

Comment 4

[Nicholas Nethercote [inactive]]

Bug 1054161's patch helps quite a bit with the scrolling speed.

Comment 6

[ISHIKAWA, Chiaki]

Attachment: Memory increase during the rendering of the link in the original post.

I am trying to see if a slow almost hung rendering issue has something in common with this bugzilla.

The problem reported here seems to have been more or less solved by now.

I am using a Windows 10 Pro PC with 32GB of memory. (AMD Ryzen 7 1700 Eight-Core Processor 3.00 GHz).

When I load the link in the original post and select the magnification to 200%, the memory usage did increase as in the attached graph (it is from the performance monitor function of task manager).
However, it is about 1.2GB and as I have already used 8GB for various applications (Firefox, VLC, adobe postscript, etc.) it was not a big deal and I did not particularly notice any sluggishness. FF's UI responded adequately. (My own problem is when UI does not respond at all. That is bad.)

Comment 7

[Kenan]

Attachment: 924072_zoomedIn200percent.JPG

Comment 8

[Kenan]

confirming with Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:97.0) Gecko/20100101 Firefox/97.0

But The speed is fine, and FF does not freeze.

The rendering of the automatic scaled view is ok, but zooming into 200% just brings the result as in comment7. It is impossible to read. Chrome works fine.
Seems not to re-render the pdf when zooming, just zooming the DOM.

Comment 9

[Marco Castelluccio [:marco]]

Zooming to a high zoom level (200% is high for this particular PDF) will fall back to CSS zoom.
I'm not sure there's much we can do here, wdyt Calixte?

Comment 10

[Calixte Denizet (:calixte)]

The problem here is the text layer itself which contains a ton of elements.
All the Firefox UI is sluggish because of that (I reported a similar bug few days ago, see bug 1813325).

Comment 11

[Frank Doty [:fdoty]]

Fx seems to be responsive although the rendering quality in comment 8 is somewhat poor