Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

PDF.js renderer crashing on transparent shapes #7675

Closed
antjkennedy opened this issue Sep 26, 2016 · 2 comments
Closed

PDF.js renderer crashing on transparent shapes #7675

antjkennedy opened this issue Sep 26, 2016 · 2 comments

Comments

@antjkennedy
Copy link

antjkennedy commented Sep 26, 2016

Link to PDF file (or attach file here): http://www.gsk.com/media/1017500/annual-report-2015.pdf

Configuration:

  • Web browser and its version: Google Chrome 53.0.2785.116 (64-bit)
  • Operating system and its version: Mac OSX 10.11.6
  • PDF.js version: Version included with extension from Chrome Web Store
  • Is an extension: Yes 1.5.294 from Chrome Web Store

Steps to reproduce the problem:

  1. Open this link http://www.gsk.com/media/1017500/annual-report-2015.pdf and the extension will crash whilst trying to render the PDF
  2. Looking through the Chrome Logs and doing some further investigation it looks like the WebGL renderer is crashing when trying to render the translucent bubbles found on some of the pages. Removing the offending pages allows the extension to render the PDF just fine.

What is the expected behavior? The PDF is rendered without crashing

good_render

What went wrong? Rendering of the PDF crashes the extension.
bad_render

Link to a viewer (if hosted on a site other than mozilla.github.io/pdf.js or as Firefox/Chrome extension): https://chrome.google.com/webstore/detail/pdf-viewer/oemmndcbldboiebfnladdacbdfmadadm

@yurydelendik
Copy link
Contributor

Able to reproduce using demo viewer at http://mozilla.github.io/pdf.js/web/viewer.html. It does not crash in 55 though. Looks like the Chrome team fixed the upstream issue. You are welcome to bisect and find when/how it was fixed.

@timvandermeij
Copy link
Contributor

Closing as fixed as it appears there is nothing else we can do here since it's already fixed upstream.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants