Unable to reproduce this issue on Ubuntu 14.04 using chrome latest stable #57.0.2987.133. By opening the pdf link from original comment observed the page loads as expected and no rendering issues is observed.

alercah@ Could you please recheck this issue by creating a new profile under chrome://settings with no apps or extensions in your browser. If issue still persists please provide a screen-cast for better understanding.

Thanks!

I tried opening it with a guest profile, with no extensions/apps. I was able to get the following consistent reproduction:

- Open a new guest profile
- Open the URl above
- While the PDF is still loading, scroll down to the second page.
- Observe the broken rendering (screenshot attached).
- Once the PDF is completed loading, scroll past the second page.
- Scroll back to the second page.
- Observe the correct rendering.

Deleted: broken.png 393 KB

	broken.png 393 KB View Download

Thank you for providing more feedback. Adding requester "brajkumar@chromium.org" to the cc list and removing "Needs-Feedback" label.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

Looks like font problem

npm@ can you take a look and see if this is a font issue?

This is a linearized PDF issue. It looks like we are not properly checking that all of the second page's content has been received. And it is rendered immediately with the first page, so we just render improperly due to missing resources. Not yet sure exactly how to fix this.

I observed the problem shown in comment 3. When I scrolled further down and then scrolled back up, the problem disappeared. Is the PDF viewer trying to draw page 2 too early, before all the necessary resources are available?

I also observed the same behaviour, and it is because the fonts seem to be missing when it first loads the page.

This is probably the same issue as  bug 624510 

Windows 7, chromium 61.0.3159.0

I'm hitting this when viewing https://www.library.cornell.edu/preservation/publications/PreservingBooks.pdf.

Starting with the 2nd page, entire lines of text are mis-rendered. Once I scroll to the bottom of the last page & start scrolling up, the text rendered "fixes" itself.

While searching for a bug I came across mention of issue 249006 which I cannot see. Is that issue related to this problem?

Workaround: pdf.js based extension doesn't exhibit this behavior

Setting PDF bugs assigned to me back to untriaged so they can get re-assigned as needed.

 Issue 624510  has been merged into this issue.

I did reproduce this a year ago, but now I can't anymore. Any tips to reset a cache or something to do it reliably? It might have been fixed in the last year.