Open Bug 1165624 Opened 5 years ago Updated 2 years ago

Memory usage 30x+ of page-size

Categories

(Firefox :: PDF Viewer, defect)

37 Branch
defect
Not set

Tracking

()

UNCONFIRMED

People

(Reporter: alexander.maznev, Unassigned)

References

(Blocks 1 open bug)

Details

(Whiteboard: [pdfjs-f-needinfo])

Attachments

(1 file)

Attached file output.txt
User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:37.0) Gecko/20100101 Firefox/37.0
Build ID: 20150420225811

Steps to reproduce:

Visit: https://github.com/JeffBezanson/phdthesis/blob/master/main.pdf
Click: Next 50 pages button
Click: Next 50 pages button

firefox 37.0.2-1 x86_64
Linux l-pc 4.0.1-1-ARCH #1 SMP PREEMPT Wed Apr 29 12:00:26 CEST 2015 x86_64 GNU/Linux



Actual results:

Firefox memory usage (especially on loading next 50 pages 2x) goes to about 1gb for a single open tab. 
Each page of the pdf is approximately a 250K.png meaning expected size is ~37.5mb. 

Linux/X-server can also behave erratically with Firefox memory problems (I've variously experienced firefox crashing, x-server crashing, x-server becoming completely unresponsive). 

Strace is attached. 



Expected results:

None of the above.
Can you reproduce the issue with another browser on github or with the built in version of pdf.js in firefox? Github uses a custom version of pdf.js, so it may be they are not cleaning up correctly.
Flags: needinfo?(alexander.maznev)
Whiteboard: [pdfjs-f-needinfo]
Yes, I have memory problems with Chromium on the same page as well, Supposing this is Github and not Firefox javascript, does Firefox not have any limits it places on what Javascript on a page can do? It seems kind of insane that a page can use 1-3gb+ memory. 

Attempting to open a local copy of the pdf with the pdf viewer set to the default Firefox introduces a new buggy behaviour. Firefox creates endless amount of tabs, and terminating Firefox causes it to restart itself and continue creating endless tabs (only deleting the file from the disk appears to stop this).
Flags: needinfo?(alexander.maznev)
You need to log in before you can comment on or make changes to this bug.