Rendering Issue in Chrome

[blackmambahk]

Attach (recommended) or Link to PDF file here:

PDF rendered using the PDFJS github demo. Some graphics are missing when rendered in Chrome as compared to FireFox

Configuration:
TestRenderingIssue.pdf

• Web browser and its version: Chrome 86.0.4240.75 (Official Build) (64-bit)
• Operating system and its version: Windows 10 latest version
• PDF.js version: 2.7.164 (PDFJS GitHUb demo viewer)
• Is a browser extension: No

Steps to reproduce the problem:

1. open attached PDF in the PDFJS github demo viewer in Chrome
   2.open attached PDF in the PDFJS github demo viewer in FireFox

What went wrong? (add screenshot)

What is the expected behavior? (add screenshot)

Note that in the screenshot of Chrome some cards (graphics) are missing

Link to a viewer (if hosted on a site other than mozilla.github.io/pdf.js or as Firefox/Chrome extension):

[Snuffleupagus]

Some graphics are missing when rendered in Chrome as compared to FireFox

That would suggest a canvas, hardware acceleration, and/or driver issue specific to Google Chrome, rather than the PDF.js library; as such it's unfortunately very difficult to see that this can be fixed here.

[blackmambahk]

Some graphics are missing when rendered in Chrome as compared to FireFox

That would suggest a canvas, hardware acceleration, and/or driver issue specific to Google Chrome, rather than the PDF.js library; as such it's unfortunately very difficult to see that this can be fixed here.

FYI it's reproducible by 15 people in 6 different companies and a whole random range of equipment, with different graphic cards and it's not an issue for the exact same people in the same browser if they use the Chrome native viewer.

[Snuffleupagus]

FYI it's reproducible by 15 people in 6 different companies and a whole random range of equipment, with different graphic cards

That'd would probably suggest a canvas-related bug in Google Chrome then...

it's not an issue for the exact same people in the same browser if they use the Chrome native viewer.

Given that PDFium (i.e. the built-in Google Chrome PDF viewer) isn't using canvas for rendering (or any part of the web-platform really), which the PDF.js library does, that's not entirely surprising either.

All-in-all, given that the PDF.js project is run by Mozilla, it's probably reasonable to expect that Google Chrome isn't the main focus of development :-)

[timvandermeij]

Closing since this looks very similar to #12502 and other very recently reported bugs. I'd strongly recommend to report this to the Chrome development team in their issue tracker instead since from the number of similar-looking reports here it looks like there may be a regression in Chrome itself, which is obviously not something we can fix.

[TMmaxx]

A workaround that we are using for the interim is turning of hardware acceleration. Definitely not ideal, but it allows our users to continue working while we work to fix the issue

[SamyCookie]

for cross references: duplicate of #12462