Closed
Bug 739180
Opened 14 years ago
Closed 13 years ago
Infinite spinning cursor for a PDF doc
Categories
(Firefox :: PDF Viewer, defect)
Firefox
PDF Viewer
Tracking
()
RESOLVED
WORKSFORME
People
(Reporter: scoobidiver, Unassigned)
References
()
Details
(Whiteboard: https://github.com/mozilla/pdf.js/issues/1453)
PDF Viewer 0.2.434.
When I try to open the ref. URL, I get a rendering error with the following message:
"PDF.JS Build: 982d58f
Message: unrecognized color space object: "undefined"
Stack: error("unrecognized color space object: \"undefined\"")@moz-filedata:939d59c3-dc36-46cf-8b53-1212ac0f8bfd:914
colorSpaceParseToIR((void 0),[object Object],[object Object])@moz-filedata:939d59c3-dc36-46cf-8b53-1212ac0f8bfd:11466
colorSpaceParse((void 0),[object Object],[object Object])@moz-filedata:939d59c3-dc36-46cf-8b53-1212ac0f8bfd:11331
isNativelySupported([object Object],[object Object])@moz-filedata:939d59c3-dc36-46cf-8b53-1212ac0f8bfd:27284
buildPaintImageXObject([object Object],true)@moz-filedata:939d59c3-dc36-46cf-8b53-1212ac0f8bfd:12650
partialEvaluatorGetOperatorList([object Object],[object Object],[object Array])@moz-filedata:939d59c3-dc36-46cf-8b53-1212ac0f8bfd:12795
pageGetOperatorList([object Object],[object Array])@moz-filedata:939d59c3-dc36-46cf-8b53-1212ac0f8bfd:236
wphSetupPageRequest(1)@moz-filedata:939d59c3-dc36-46cf-8b53-1212ac0f8bfd:28833
messageHandlerComObjOnMessage([object MessageEvent])@moz-filedata:939d59c3-dc36-46cf-8b53-1212ac0f8bfd:28767"
| Reporter | ||
Comment 1•14 years ago
|
||
In today's front page (March 29th), it's an infinite spinner icon.
| Reporter | ||
Updated•14 years ago
|
Whiteboard: https://github.com/mozilla/pdf.js/issues/1453
| Reporter | ||
Updated•14 years ago
|
Summary: PDF rendering error: unrecognized color space object: "undefined" → Infinite spinning cursor for a PDF doc
| Reporter | ||
Comment 2•13 years ago
|
||
I can't reproduce neither with PDF Viewer 0.4.37, nor with 18.0a1/20120829.
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → WORKSFORME
You need to log in
before you can comment on or make changes to this bug.
Description
•