Closed Bug 1164199 Opened 10 years ago Closed 10 years ago

PDFs not rendered, with "Security Error: Content at resource://pdf.js/web/viewer.html may not load data from blob:null/" and "Error during JPEG image loading pdf.js:235"

Categories

(Firefox :: PDF Viewer, defect, P2)

defect

Tracking

()

VERIFIED WORKSFORME
Tracking Status
firefox40 + fixed
firefox41 + fixed

People

(Reporter: guijoselito, Assigned: baku)

References

Details

(Keywords: regression, Whiteboard: [pdfjs-c-integration])

http://desantoandre.edunet.sp.gov.br/ATRIBUI%C3%87%C3%83O%202013/2015/Edital%20docentes%20qualificados%20-%2018-05-2015.pdf http://desantoandre.edunet.sp.gov.br/ATRIBUI%C3%87%C3%83O%202013/2015/Edital%20Docentes%20Habilitados%2015-05-2015.pdf This is what I get on browser console: PDF 1526020dc97b029ab2261b381dc57549 [1.5 Lexmark X658de / HardCopy] (PDF.js: 1.1.114) viewer.js:6397:1 Security Error: Content at resource://pdf.js/web/viewer.html may not load data from blob:null/f11cccb2-0412-4574-a692-99ab5653f0b7. Warning: Error during JPEG image loading pdf.js:235:5 Warning: Dependent image isn't ready yet Chrome 42 and Firefox 38 display the PDF just fine.
Summary: PDFs not rendered → PDFs not rendered, with "Security Error: Content at resource://pdf.js/web/viewer.html may not load data from blob:null/" and "Error during JPEG image loading pdf.js:235"
[Tracking Requested - why for this release]: [Tracking Requested - why for this release]: Pushlog: https://hg.mozilla.org/integration/mozilla-inbound/pushloghtml?fromchange=81b2c07f94ef&tochange=522f3549ec5b Regressed by: Bug 1156875
Blocks: 1156875
Flags: needinfo?(amarchesini)
Problem with FF Dev Edition 40 with me. I saw nothing at all, in the sample PDF that Daniel Holbert linked to. Here I have two links to PDFs--the text is read just fine, but graphics at the top of each are not displayed at all (they are displayed if the PDFs are downloaded): http://www.paulrittman.com/FallofSovietUnionTimeline.pdf http://www.paulrittman.com/AntitrustChart.pdf
(In reply to Guilherme Lima from comment #0) Side note: > Security Error: Content at resource://pdf.js/web/viewer.html may not load > data from blob:null/f11cccb2-0412-4574-a692-99ab5653f0b7. This part seems like it might be an (expected) regression from bug 1086999. (I don't think it's involved with the mis-rendering, though.)
(In reply to Daniel Holbert [:dholbert] from comment #5) > This part seems like it might be an (expected) regression from bug 1086999. > (I don't think it's involved with the mis-rendering, though.) It is unlikely. My bisect results agree with comment 2.
Tracking this regression for 40+.
Priority: -- → P2
Whiteboard: [pdfjs-c-integration]
Definitely this bug is a regression from bug 1156875. A fix should land soon.
Assignee: nobody → amarchesini
Flags: needinfo?(amarchesini)
OS: Windows 7 → All
Hardware: x86_64 → All
bug 1168547 fixed this. Anything else is going to be done here?
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → DUPLICATE
(In reply to Guilherme Lima from comment #16) > bug 1168547 fixed this. Anything else is going to be done here? This bug does not contain the fix for the issue. (In reply to Andrea Marchesini (:baku) from comment #17) > > *** This bug has been marked as a duplicate of bug 1168547 *** Fixed somewhere else. Marking as WFM.
Flags: needinfo?(amarchesini)
Resolution: DUPLICATE → WORKSFORME
Flags: needinfo?(amarchesini)
Andrea, is this actually resolved for 40? I notice this bug is marked as affected in 40, but in bug 1168547, the update to pdf.js was only for 41.
Flags: needinfo?(amarchesini)
FWIW, using today's FDE build, the two links I gave above WFM. Graphics are being displayed along with text, which wasn't the case before.
(In reply to Liz Henry (:lizzard) from comment #19) > Andrea, is this actually resolved for 40? It is indeed; PDFs from comment 1 and comment 2 all render correctly in latest version of Firefox 40 dev edition, on Linux. 40.0a2 (2015-06-13) (Ping me if you have further questions about this.)
Status: RESOLVED → VERIFIED
Flags: needinfo?(amarchesini)
You need to log in before you can comment on or make changes to this bug.