Pdf.js: Chrome does not render PDF - Bad end offset

Created on 8 Sep 2016 · 12Comments · Source: mozilla/pdf.js

http://www.boarddocs.com/ny/pobcsd/Board.nsf/files/ADDNFU5FC4AB/$file/Smart%20Schools%20Investment%20Plan%20PresentationSeptember%207%20%202016%20v3.pdf

Configuration:

Chrome 53.0.2785.101
Windows 10 x64
PDF.js 1.5.294

The above PDF opens properly in Firefox 48.0.2 on the same computer, decently fast. However, when loading it in the Chrome extension, the loading bar on top fills and a blank screen is shown (see screenshot). Console shows the following:

pdf.worker.js:2311 Error: Bad end offset: 3465432
pdf.worker.js:2312     at error (chrome-extension://oemmndcbldboiebfnladdacbdfmadadm/content/build/pdf.worker.js:2312:17)
    at assert (chrome-extension://oemmndcbldboiebfnladdacbdfmadadm/content/build/pdf.worker.js:2327:5)
    at Object.ChunkedStream_onReceiveData [as onReceiveData] (chrome-extension://oemmndcbldboiebfnladdacbdfmadadm/content/build/pdf.worker.js:6069:7)
    at Object.ChunkedStreamManager_onReceiveData [as onReceiveData] (chrome-extension://oemmndcbldboiebfnladdacbdfmadadm/content/build/pdf.worker.js:6478:21)
    at Object.<anonymous> (chrome-extension://oemmndcbldboiebfnladdacbdfmadadm/content/build/pdf.worker.js:6331:14)

2016-09-08_15-22-02

Source

szheng95

Most helpful comment

@ksn135 There is a "Disable range requests" option - try toggling it.

szheng95 on 4 Aug 2017

👍3

All 12 comments

@Rob--W Are you able to reproduce this? I don't see how this would be different in the Chrome extension, unless it's fixed recently and not yet included in the release.

timvandermeij on 8 Sep 2016

Update - check to see if the URL has to do with it. I downloaded the file and uploaded it to a different location, and it opened. But that could also have to do with different server, etc.

szheng95 on 8 Sep 2016

It might be that the server is not serving the file properly. I wonder why that only affects Chrome then.

timvandermeij on 8 Sep 2016

@szheng95 it's related to how caching is working. if you disable caching in chome the extension will load the URL in the description. We had similar problems in the past, see https://github.com/mozilla/pdf.js/issues/5512 (but now I think it returns 200 instead of 206 for tail request)

yurydelendik on 8 Sep 2016

@yurydelendik Yes, disabling caching is working, but obviously doing so for the entire browser is not a practical workaround. Is there a way to disable caching only for pdf.js? I seem to be running into this problem more and more lately, though that may just be a function of the sites I'm frequenting.

szheng95 on 12 Dec 2016

Same problem. Any solutions?

ksn135 on 4 Aug 2017

Workaround: add 59 and 60 chrome version to condition in web/compatibility.js line 34:
var isChromeWithRangeBug = /Chrome\/(39|40|59|60)\./.test(userAgent);

ksn135 on 4 Aug 2017

@ksn135 There is a "Disable range requests" option - try toggling it.

szheng95 on 4 Aug 2017

👍3

@szheng95 Thanks!

ksn135 on 4 Aug 2017

I'm also seeing this error with the latest chrome extension release when I try to open http://www.mckinsey.com/~/media/McKinsey/Industries/Advanced%20Electronics/Our%20Insights/How%20artificial%20intelligence%20can%20deliver%20real%20value%20to%20companies/MGI-Artificial-Intelligence-Discussion-paper.ashx. In Firefox, the PDF prompts for download instead of opening in the PDF viewer.

UPDATE: confirmed that disabling range requests seems to fix it - thanks!

diracdeltas on 12 Sep 2017

How i can disable the "range request", whats is that?? a command?? a code on a js?? how??

Omazon on 20 Sep 2017

This looks like a duplicate of issue #9544, which according to https://github.com/mozilla/pdf.js/issues/9544#issuecomment-374176371 was a (now fixed) upstream bug in Google Chrome.