1374945 - stack exhaustion loading pdf

Status: NEW

(Firefox :: PDF Viewer, defect, P3)

Description

[Raphael]

Attachment: poc.pdf

User Agent: Mozilla/5.0 (Windows NT 6.1; rv:55.0) Gecko/20100101 Firefox/55.0
Build ID: 20170619071723

Steps to reproduce:

Open Poc.pdf


Actual results:

Crash reports:
https://crash-stats.mozilla.com/report/index/2a9266de-3b54-457e-94de-590d80170621#tab-details

Comment 1

[YF (Yang)]

I see the memory grows fast but does not see a crash.

Comment 2

[Daniel Veditz [:dveditz]]

Looks like the reporter has 2GB of memory, a lot less than our developer machines. Could easily believe he's run out of stack space on a testcase where we wouldn't.

Comment 3

[Brendan Dahl [:bdahl]]

I'm not sure why the above is tagged as PDFium as this seems to be a pdf.js issue.

Comment 4

[Wayne Mery (:wsmwk)]

Raphel, can you still reproduce using a current version?

Comment 5

[YF (Yang)]

Reproducible.

Comment 6

[YF (Yang)]

Regression range:
https://hg.mozilla.org/mozilla-central/pushloghtml?fromchange=8122ffa9e1aa&tochange=d01bf8596d3b

0c2a1ea6a296	Yury Delendik — Bug 979909 - Update pdf.js to version 0.8.1114. r=Mossop

Comment 7

[Wayne Mery (:wsmwk)]

nice find

Comment 8

[Liz Henry (:lizzard) (relman/hg->git project)]

Too late to fix for 58. If anyone comes up with a fix, we can take a patch in Nightly (currently 60)

Comment 9

[Ryan VanderMeulen [:RyanVM]]

Still causes a pretty big memory spike on load, but the usage goes down pretty quickly again once it finishes loading.

Comment 10

[Marco Castelluccio [:marco]]

(In reply to Ryan VanderMeulen [:RyanVM] from comment #9)

Still causes a pretty big memory spike on load, but the usage goes down pretty quickly again once it finishes loading.

I can still reproduce this on Linux in Nightly 97.
Brendan can reproduce this on Mac in Nightly 97.
Calixte can reproduce this on Windows in ESR 91, can't reproduce this on Windows in Nightly 97.

Comment 11

[Kenan]

WIth Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:100.0) Gecko/20100101 Firefox/100.0

it is loading for several minutes (until I stopped the tab). In the first 60 sec of loading the memory usage comes up to about 2-2.5 GB.

I also could not find a different behaviour in the release before the regression, mentioned above.

Comment 12

[Kenan]

but the poc.pdf contains a JPX coded image with W=32765 and H=32765 with 8 BPP. (Info from Acrobat), while the object browser tells me:

XObject (dict)
    Im0 (stream) [id: 5, gen: 0]
        BitsPerComponent = 8
        ColorSpace = /DeviceGray
        Filter (array)
        Height = 57
        Length = 1402
        Subtype = /Image
        Type = /XObject
        Width = 1200