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

Error in opening PDF file #9934

Closed
sridhard opened this issue Jul 28, 2018 · 4 comments
Closed

Error in opening PDF file #9934

sridhard opened this issue Jul 28, 2018 · 4 comments

Comments

@sridhard
Copy link

sridhard commented Jul 28, 2018

Attach (recommended) or Link to PDF file here:
https://d29xdxvhssor07.cloudfront.net/testfolder/video/error.pdf

Configuration:

  • Web browser and its version: Chrome, 67.0.3396.99
  • Operating system and its version: Mac OS 10.13.5 (17F77)
  • PDF.js version: we tried with hosted demo
  • Is a browser extension: No

Steps to reproduce the problem:

  1. Just open the file using PDF JS, https://mozilla.github.io/pdf.js/web/viewer.html?file=https://d29xdxvhssor07.cloudfront.net/testfolder/video/error.pdf

What is the expected behavior? (add screenshot)
PDF should display success. Chrome native PDF viewer is displaying properly. Other viewers like adobe viewer, android native viewer are displaying this PDF properly.

What went wrong? (add screenshot)
PDF giving error

Link to a viewer (if hosted on a site other than mozilla.github.io/pdf.js or as Firefox/Chrome extension):
https://mozilla.github.io/pdf.js/web/viewer.html?file=https://d29xdxvhssor07.cloudfront.net/testfolder/video/error.pdf

@timvandermeij
Copy link
Contributor

The console shows inconsistent generation in XRef.

@sridhard
Copy link
Author

Yes. But all other PDF viewers are able to display it. So it is better if pdfjs consider this and recover the broken xref.

Many pdf editors/writers are generating these kind of docs. The one we share is generated with foxit which is one of the popular writer/editor

@timvandermeij
Copy link
Contributor

Indeed, we always try to recover data if we can. Marking as corrupted PDF for now so we can look into have to address this.

@timvandermeij
Copy link
Contributor

Closing since the PDF file is not available anymore and we just landed a commit that might have fixed this in #10392.

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

2 participants