1260585 - PDF render fails with matlab-rendered image

Status: RESOLVED FIXED

(Firefox :: PDF Viewer, defect, P3)

Description

[kwalsh]

Attachment: err.pdf

User Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/49.0.2623.87 Safari/537.36

Steps to reproduce:

View the attached PDF with builtin PDF viewer


Actual results:

Image within PDF renders slowly as a sequence of many thousands of seemingly randomly-colored rectangles and random lines.


Expected results:

Image should have rendered as a nice, red/blue-shaded curved 3D graphic, as it appears in Adobe Reader, Chrome's PDF viewer, Inkscape, and other similar PDF viewers.

Comment 1

[Alice0775 White]

Regression window:
Good but no shading color:
https://hg.mozilla.org/integration/fx-team/rev/13cfa6b095a0
Mozilla/5.0 (Windows NT 6.1; WOW64; rv:42.0) Gecko/20100101 Firefox/42.0 ID:20150806095258

Bad(completely broken)
https://hg.mozilla.org/integration/fx-team/rev/7216b345380e
Mozilla/5.0 (Windows NT 6.1; WOW64; rv:42.0) Gecko/20100101 Firefox/42.0 ID:20150806121442

Pushlog:
https://hg.mozilla.org/integration/fx-team/pushloghtml?fromchange=13cfa6b095a0&tochange=7216b345380e

Regressed by: 	1a75b4e0ac8b	Ryan VanderMeulen — Bug 1188344 - Update pdf.js to version 1.1.366. r=bdahl

Comment 2

[Jim Mathies [:jimm]]

Yuri, do you want to track this?

Comment 3

[Yury Delendik (:yury)]

It's interesting that it is working in PDF.js in Safari.

Temporary workaround at https://github.com/mozilla/pdf.js/pull/7184, filing upstream issues.

(In reply to Alice0775 White from comment #1)
> Good but no shading color:

> Regressed by: 	1a75b4e0ac8b	Ryan VanderMeulen — Bug 1188344 - Update pdf.js
> to version 1.1.366. r=bdahl

Bug 1188344 adds support for mesh types, so it's not really are regression since in before and after cases rendering was incorrect.

Comment 4

[Yury Delendik (:yury)]

Filed https://bugs.chromium.org/p/chromium/issues/detail?id=602509 and https://bugzilla.mozilla.org/show_bug.cgi?id=1263776

Comment 5

[Jim Mathies [:jimm]]

needs an owner

Comment 6

[Jet Villegas (inactive)]

Ryan: Bug 1263067 just missed PR #7184 that fixes this bug for us (see comment 3.) Please mark this bug fixed when you land the next "Update pdf.js to version 1.x" bug. Thanks!

Comment 7

[Ryan VanderMeulen [:RyanVM]]

Should be fixed on trunk now.

Comment 8

[Yury Delendik (:yury)]

Jet, I think you meant to be NI'ed on bug 1263776 at comment 5.

Comment 9

[Lawrence Mandel [:lmandel] (use needinfo)]

We've let this ride in a couple of releases. 47 is marked as affected and hasn't shipped. Should we take this fix in 47?

Comment 10

[Md. Rahimul Islam]

I have successfully reproduce this bug on firefox nightly 48.0a1 (2016-03-29)
(Build ID: 20160329030246)
with windows 7 (32 bit)

I found this fix on latest beta 48.0b2

Mozilla/5.0 (Windows NT 6.1; rv:48.0) Gecko/20100101 Firefox/48.0
Build ID : 20160620091522

[bugday-20160622]

Comment 11

[Md.Tarikul Islam Oashi]

I have reproduced the bug on Firefox Nightly 48.0a1 (2016-03-29) with Linux Mint 64 bit.

The Bug's fix is verified on Latest beta 48.0b7

Build ID      20160711002726
User Agent    Mozilla/5.0 (X11; Linux x86_64; rv:48.0) Gecko/20100101 Firefox/48.0

[bugday-20160713]

Comment 12

[Rezaul Huque Nayeem]

As this bug is verified on Windows (Comment 10) and Linux (Comment 11), marking this as verified !

Comment 13

[Timea Cernea [:tbabos][inactive]]

Reopening this issue since it can be reproduced on latest Nightly 68.0a1 (2019-04-02) (64-bit) on Mac OS 10.13.
On windows and linux it is also loading in 2-3 seconds but MacOS seems to be the most affected. Check: https://streamable.com/80x4n

Comment 14

[Julien Cristau [:jcristau] (back April 22)]

After 3 years it may be better to file a new bug for comment 13...

Comment 15

[Daniel Bodea [:danibodea]]

(In reply to Julien Cristau [:jcristau] from comment #14)

After 3 years it may be better to file a new bug for comment 13...

I have logged a new bug for this issue with all relevant information: bug 1580739.
Closing this one as its previous status: RESOLVED FIXED. Thanks.