Printed sample.pdf and it looks fine on paper - see a scan of my printout attached. Version is 61.0.3163.100 (Official Build) (64-bit)

Looks like a printing issue

Deleted: 20171024153300192.pdf 39.7 KB

20171024153300192.pdf 39.7 KB Download

I'll take a look. Might be related to the large number of image masks in the PDF. Were there issues with this in Chrome 60?

Chrome 60 works, as does 61. In 62 printing is broken. 
Tested with 62.0.3202.62 official build, 64bit.

Thank you for providing more feedback. Adding requester "rbpotter@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

The following revision refers to this bug:
  https://pdfium.googlesource.com/pdfium/+/78b334a824c42138f5e98060638b1643b0279602

commit 78b334a824c42138f5e98060638b1643b0279602
Author: rbpotter <rbpotter@chromium.org>
Date: Wed Oct 25 23:16:37 2017

Temporarily disable mask rendering again

Bug:  chromium:777837 
Change-Id: I1830dc37b9c039a95509627026461134d8f2c16d
Reviewed-on: https://pdfium-review.googlesource.com/16710
Reviewed-by: Lei Zhang <thestig@chromium.org>
Commit-Queue: Rebekah Potter <rbpotter@chromium.org>

[modify] https://crrev.com/78b334a824c42138f5e98060638b1643b0279602/fpdfsdk/fpdfview.cpp

Able to reproduce issue on reported version 62.0.3202.62 and Latest beta 63.0.3239.18  but its not reproducible on latest Canary M-64(64.0.3251.0) using Win 10, looks like the issue is fixed on Latest Canary 64.0.3251.0. Hence adding TE-Verified-M64 label
Please find the attached screenshot.

Adding the M-62 RB-Stable in case we plan any stable refresh to get the fix merged to M-62

Attaching screenshot of printed sample PDF of both 62.0.3202.62(content missing) and 64.0.3251.0(content seen)

Deleted: IMG_20171027_145736.jpg 4.3 MB

	IMG_20171027_145736.jpg 4.3 MB View Download

rbpotter@, thank you for the fix. Please go ahead and request a merge ASAP if this fix needs to be on M62 as we'll have M62 re-spin (most likely) this week.

Requesting M-63 merge for now.

This bug requires manual review: M63 has already been promoted to the beta branch, so this requires manual review
Please contact the milestone owner if you have questions.
Owners: cmasso@(Android), cmasso@(iOS), gkihumba@(ChromeOS), govind@(Desktop)

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

Approving merge to M63 branch 3239 based on comment #8. Please merge ASAP so we cna take in for this week Beta release. Thank you.

[Bulk Edit]
URGENT - PTAL.
M63 Stable promotion is coming soon and your bug is labelled as Stable ReleaseBlock, pls make sure to land the fix and get it merged into the release branch ASAP. Thank you.

The following revision refers to this bug:
  https://pdfium.googlesource.com/pdfium/+/a8caf1c23a8376705d8cb08500d82aa6e948a082

commit a8caf1c23a8376705d8cb08500d82aa6e948a082
Author: Lei Zhang <thestig@chromium.org>
Date: Mon Oct 30 21:58:04 2017

M63: Temporarily disable mask rendering again

Bug:  chromium:777837 
TBR=rbpotter@chromium.org

Change-Id: I1830dc37b9c039a95509627026461134d8f2c16d
Reviewed-on: https://pdfium-review.googlesource.com/16710
Reviewed-by: Lei Zhang <thestig@chromium.org>
Commit-Queue: Rebekah Potter <rbpotter@chromium.org>
(cherry picked from commit 78b334a824c42138f5e98060638b1643b0279602)
Reviewed-on: https://pdfium-review.googlesource.com/17190
Commit-Queue: Lei Zhang <thestig@chromium.org>

[modify] https://crrev.com/a8caf1c23a8376705d8cb08500d82aa6e948a082/fpdfsdk/fpdfview.cpp

My recommendation right now is to wait until M63 since issue doesn't seem quite as prevalent. Removing RBS label for now; but we can re-visit if this issue spikes as we ramp-up M62. 

+RBS. On a second thought, adding RBS for now for tracking. 

M63 Stable promotion is coming soon and your bug is labelled as Stable ReleaseBlock, pls make sure to land the fix and request a merge to M63 ASAP. Thank you.

Fix was merged to M63 already. See comment 15.

Yeah, sorry it was a bulk edit. Could you pls mark the bug as fixed if nothing is pending?

Marking fixed since this is fixed in M63.

We have customer reporting the same issue, is there a chance to fix this in M62, as M63 release is not that close.

+ abdulsyed@ (Chrome Desktop M62 TPM), PTAL comment #23. Thank you.

This is a relatively small change that reverts to M59 (and earlier) behavior, and has been in Canary/Dev/Beta for over a week so it should be safe to merge. Given issue reports seem to have increased with the ramp-up of M-62, requesting merge for M62.

Thanks rbpotter@ for the fix. Upon more examination, we have received only 3 reports, we've been at 25% for more than a week, and it's affecting only a very small subset of pdfs. There is a clear workaround (download the PDF and use a PDF reader). Rejecting this merge for M62 since we're already ramping up and this is not an absolutely critical P0 issue.

M63 will contain the fix. In the meantime, if customers face this issue, please provide workaround solution. 

 Issue 785380  has been merged into this issue.

You can add me to the list of people requesting for this to be fixed sooner than later.  We have seen this with many different PDFs within our organization, and it is affecting a lot of users.  Is there any way to revert to the older version and keep it from updating itself?  Thank you.

 Issue 786973  has been merged into this issue.

 Issue 787052  has been merged into this issue.

Please add me to those requesting an earlier fix. This issue is compromising our ability to transition our teachers, staff, and students to use Google Chrome instead of Internet Explorer, as a number of our instructional programs rely heavily on the ability to print cloud-hosted PDFs.

I already requested to be included with those asking for an earlier fix, but I just wanted to add this:  there seems to be a low priority placed on this fix based on comments above, and I do not understand this.  Based on what the comment above me said, and what I am seeing myself, this is a major issue.  Many of our users are unable to use Chrome effectively without a workaround, and instructing them all in the use of workarounds may work for some, but for others it can be quite a confusing issue.  Without a simple way to fix it for everyone now, we are starting to question our choice to use Chrome as our main browser here.  I don't think that's what Google wants is for issues like these to make people question their choice in browsers.

Separate from the discussion on whether the merge of the fix to M62 should have happened or not, I would like to point out it is really hard to test the combination of all possible PDFs with all possible printers. If you are responsible for an organization with lots of users, it would be extremely helpful if you run Chrome Beta or Dev channel, and try to use that channel for every day tasks that are deemed business critical. If you notice something is wrong and file a bug, we will have a better chance of catching it before it hits Stable channel.

Please see this "Chrome release best practices" article for more details: https://support.google.com/chrome/a/answer/6025002

Just to update the latest behavior on beta.

Tested this issue on Windows 7 using chrome latest beta-63.0.3239.59 as per C#0.

Able to print above attached (sample.pdf) clearly without any missing content.Also tried below sample URL's which are also printed text without any text missing issue.

http://css4.pub/2015/textbook/somatosensory.pdf
http://www.pdf995.com/samples/pdf.pdf

Thanks..!

 Issue 785401  has been merged into this issue.

 Issue 789536  has been merged into this issue.