Some PDF graphics/images have black circles rendered in the upper left corner with hardware acceleration enabled

NEW
Unassigned

Status

()

P3
normal
6 years ago
a month ago

People

(Reporter: ron.bakus, Unassigned)

Tracking

20 Branch
x86_64
Windows 7
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

(Whiteboard: [pdfjs-c-rendering][pdfjs-d-hwa-on])

Attachments

(4 attachments)

(Reporter)

Description

6 years ago
Created attachment 733411 [details]
black circles.png

User Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:20.0) Gecko/20100101 Firefox/20.0
Build ID: 20130326150557

Steps to reproduce:

Attempted to read PDF located at http://ac.els-cdn.com/S0960894X13003442/1-s2.0-S0960894X13003442-main.pdf?_tid=919e5e40-9d46-11e2-aa9f-00000aab0f27&acdnat=1365093899_8f9fd616060dd85e7e70df0a61b39a54 (accessed from http://www.sciencedirect.com/science/article/pii/S0960894X13003442# by clicking on the PDF option on the page, resulting in new browser window popping up with PDF loaded within).


Actual results:

After loading, second page was not rendered.  By changing the zoom, the second page rendered, but all graphics/images had black circles rendered in the upper left corner (see attached screen shot).  The latter may be related to https://bugzilla.mozilla.org/show_bug.cgi?id=837461


Expected results:

PDF should have rendered correctly.  PDF renders correctly in acrobat reader.
(Reporter)

Updated

6 years ago
Summary: Some pages of PDFs not rendered with PDF.js → Some pages of PDFs not rendered with PDF.js, can be triggered to render, but breaks graphics rendering

Updated

6 years ago
Component: Untriaged → PDF Viewer

Comment 1

6 years ago
Created attachment 733434 [details]
PDF sample

I attached the PDF document because the website is very slow.

Comment 2

6 years ago
Same result with FF20 and FF23, black circles in the upper left corner of graphics are visible.

It appears only with HWA enabled.
Summary: Some pages of PDFs not rendered with PDF.js, can be triggered to render, but breaks graphics rendering → Some PDF graphics/images have black circles rendered in the upper left corner with hardware acceleraytion enabled

Updated

6 years ago
Summary: Some PDF graphics/images have black circles rendered in the upper left corner with hardware acceleraytion enabled → Some PDF graphics/images have black circles rendered in the upper left corner with hardware acceleration enabled
Confirmed with Mozilla/5.0 (Windows NT 6.1; WOW64; rv:23.0) Gecko/20130405 Firefox/23.0 ID:20130405103453 CSet: 40a228f74389 + PDF.js 0833.
Status: UNCONFIRMED → NEW
Ever confirmed: true
Priority: -- → P3
Whiteboard: [pdfjs-c-rendering][pdfjs-d-hwa-on]

Comment 4

5 years ago
Created attachment 829270 [details]
Black patch with FF.png

Seen with FF 24, 25, 26 beta.
-Vin
Created attachment 8552490 [details]
Minimal test case to reproduce the issue
Duplicate of this bug: 1124116
It is specific to Windows graphics backend. PDF contains command moveTo(0,0)/lineTo(0,0)/closePath/stroke (see attached html) and that causes to draw a circle on Windows.
Component: PDF Viewer → Graphics
Product: Firefox → Core

Comment 8

4 years ago
Thx Yury!
I tried with FF 36 beta 1 & not able to recreate the issue.
So, does it mean that the issue has been resolved?
Appreciate the effort.
-Vin
(In reply to Vin from comment #8)
> Thx Yury!
> I tried with FF 36 beta 1 & not able to recreate the issue.
> So, does it mean that the issue has been resolved?

I can still see the issue on FF 38 with PDFs and minimal test case. Make sure you are using hardware acceleration (check that at about:support).

Comment 10

4 years ago
Do have "Use hardware acceleration when available" checked.
Have tried with few different articles & could not reproduce with FF 36 beta 1 & FF 34.
Been a while that the issue was recreated...maybe few months ago.
So, not sure what has been updated to resolve this?
-Vin

Comment 11

4 years ago
Still a problem on my machine, Windows 7 SP1 with hardware acceleration on. I tried FF34 and FF 36b1 after your post Vin.

Comment 12

4 years ago
Ok, Nathan reminded me that this was only with the FF PDF Viewer...not sure why I forgot that...maybe been a while...so, yes, it still appears...work to do...:)
-Vin

Comment 13

4 years ago
Going through the plugins, noticed that FF PDF Viewer (PDF.JS) is no longer compatible with FF 35 onwards.
https://addons.mozilla.org/ro/firefox/addon/pdfjs/?src=userprofile

Then this bug would be laid to rest?
If yes, then, as the plugin is not removed, the issue still comes up with FF PDF Viewer being default.
The solution being uninstalling the plugin manually.
Is there a plan to remove it completely with any new forthcoming versions?
If this is not the right place for this, appreciate if you can direct to the appropriate group/person.
Thx.
-Vin

Comment 14

4 years ago
Got an update on the support forum, seems a new version of the viewer is available on github, which is compatible with new versions of FF.
Off-course that doesn't solve our black patch issue.
Sorry for any confusion.
-Vin
Duplicate of this bug: 1180521
Duplicate of this bug: 1234016

Comment 18

a year ago
This issue remains in FF 54.0.1

Chrome has black lines the same vertical dimension as FF's ellipses.

Comment 19

10 months ago
The issue with the black circles in the upper left corner of figures still persists in Firefox 58.0.2. This is annoying. The issue occurs, for example, if I open the pdf version of this paper:

https://www.sciencedirect.com/science/article/pii/S0016718514001444

I wonder why this issue has not been resolved for 5 years (?).

Comment 20

a month ago
I am pretty sure this problem is exclusive to Elsevier (the scientific publishers) PDFs. I can recreate the problem using Elsevier created documents with other PDF viewers (not related to Mozilla) such as the chrome black line, or the circle effect in Edge. I think it is unrelated to the Mozilla viewer, and instead an error created when Elsevier embeds graphics into their PDFs.

Elsevier is so tight on cash that I doubt they will be able to pay someone to fix it.
You need to log in before you can comment on or make changes to this bug.