New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 788864 link

Starred by 16 users

Issue metadata

Status: Fixed
Owner:
Closed: Nov 2017
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Windows
Pri: 2
Type: Bug-Regression



Sign in to add a comment

Missing text lines when printing specific PDF files in Chrome

Project Member Reported by llinares@chromium.org, Nov 27 2017

Issue description

Version of Google Chrome (Wrench-> About Google Chrome):
62.0.3202.94 (Official Build) (64-bit) (64-bit) (Cohort: Stable)
64.0.3278.0  (Official Build) canary (64-bit) (Cohort: Clang-564)

OS: (e.g. Win7, OSX 10.9.5, etc...)
Windows 10, Windows 8.1 and Windows 7

Version of MSI (if applicable): No
Using group policy settings? No

What steps will reproduce the problem?
(1) Open the PDF file provided in this thread.
(2) Print the file to any printer.


What is the expected result?
-All text lines and character should be printed.

What happens instead?
-Some text lines from the PDF are missing in the output.

Please use labels and text to provide additional information.
-The issue is not reproducible when the PDF is opened/printed using the extension "PDF Viewer". https://chrome.google.com/webstore/detail/pdf-viewer/oemmndcbldboiebfnladdacbdfmadadm?hl=en
-This issue can only be reproducible with certain types of PDF files. The sample provided comes from a ticketing system that encodes these files.
-The issue doesn't happen on other browsers. IE, Firefox.
-PDF file and logs can be found at https://drive.google.com/open?id=1dZRe4DGeyy7eWFAYRZZKQluRvyzjqaoL 

 
Components: Internals>Printing Internals>Plugins>PDF
Labels: -Pri-3 Needs-Bisect Needs-Triage-M64 Pri-2
Cc: vamshi.k...@techmahindra.com
Labels: Triaged-ET Needs-Feedback
"Thanks for filing the issue.

@Reporter: Could you please provide a sample pdf file as the link provided in comment#0 is not accessible from our end.
"

Comment 3 Deleted

We have the same or similar issue in Chrome 62 that our users have started reporting. On our Xerox copier we have a setting under scan to email called MRC compression. Default is set on,  it appears fine when opened in Chrome, but when you print it from chrome it fails to print correctly.  If I turn that setting off and resend the scan to email,  Chrome prints it fine..., if I change the default setting to 3 layer compression it prints fine.  If I leave at it's which is on the copiers default  but download and open in adobe PDF viewer on the windows machine, it prints fine. Testing under Canary version 64XXXX and the issue does not seem to be there. I am hoping the issue will be addressed in Chrome 63 but I don't know that.
Comment 3 - given your issue is with PDFs generated by a scanner and is fixed on Canary, you are probably seeing  bug 777837 , which is fixed in 63. You can verify this by testing with Chrome Beta (currently 63). This bug is something separate since the reporter is saying it also occurs on Chrome 64 (Canary).
I have the same problem with Kyocera Copiers and printing PDF's from the native Chrome PDF viewer. My users have to download the PDF and print using Adobe or other.
All bug reporters - please only comment/star this issue if you are seeing the same problem originally reported and, like the original bug reporter, you are still having the same problem in Chrome Beta or Canary. If this is the case, it would help if you can attach a sample PDF that is not printing correctly.

If printing works in Beta and Canary, and the issue is only with certain PDFs,  bug 777837  is probably your bug. It is already fixed on Canary/Beta and the fix will be on Stable some time in the next couple weeks when 63 is released.

Even though the two bugs have similar symptoms, we need to keep the discussions separated since 777837 has already been addressed, while this issue still needs to be fixed.
Status: Untriaged (was: Unconfirmed)
Able to reproduce this on Windows 10 on 62.0.3202.94 and 64.0.3278.0. Need to check older builds to see if this is a regression or not.
Labels: -Type-Bug -Needs-Feedback Type-Bug-Regression
Labels: -Needs-Bisect -Needs-Triage-M64
The regression range is https://chromium.googlesource.com/chromium/src/+log/4d4c5fb..2c5e4da, so it's most likely r415766, which means there's a 50/50 chance it's my fault.
Cc: vkhabarov@google.com
Labels: Hotlist-Enterprise
Seeing same issue on Win 7 v62
Cannot confirm Beta or Canary as this is a corporate shop.
Cannot attach sample as this is confidential material.

This is affecting production and needs to get resolved ASAP.

Comment 13 Deleted

Comment 14 by weili@chromium.org, Nov 29 2017

Owner: thestig@chromium.org
Status: Assigned (was: Untriaged)
I did bisect on pdfium, it is https://pdfium.googlesource.com/pdfium.git/+/21b111fcf71e4e189035f29606ca9d3fdf3ebd92, assign to thestig@

Btw, the pdf from OP can't print at all from canary. The printed page shows "ERROR: undefined
 OFFENDING COMMAND: mTj"
So there are probably more problem to investigate.

 Issue 789565  has been merged into this issue.
The "offending command" issue only happens with PostScript printing, not with all printers. However it works on Beta and Stable, so something changed between 63 and 64. 
I'll take this bug, but given the PDF for this bug is having even more problems on Canary, we should file separate bugs and investigate the other issues.
Project Member

Comment 18 by bugdroid1@chromium.org, Nov 30 2017

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

commit 247c0e05dacb3b958bb7aaf06f21b93e78c43e19
Author: Lei Zhang <thestig@chromium.org>
Date: Thu Nov 30 18:56:00 2017

Relax checks in CFX_FaceCache::LoadGlyphPath().

The original fix to  https://crbug.com/641333  was too strict. Relax the
checks and use a std::tuple for the path map key, instead of trying to
"hash" a key.

BUG= chromium:788864 

Change-Id: I6e6a96691bce2834c2e95baa16ebd39e6aa03140
Reviewed-on: https://pdfium-review.googlesource.com/19950
Reviewed-by: dsinclair <dsinclair@chromium.org>
Commit-Queue: Lei Zhang <thestig@chromium.org>

[modify] https://crrev.com/247c0e05dacb3b958bb7aaf06f21b93e78c43e19/core/fxge/cfx_facecache.cpp
[modify] https://crrev.com/247c0e05dacb3b958bb7aaf06f21b93e78c43e19/core/fxge/cfx_facecache.h

Status: Fixed (was: Assigned)
If there are new / other issues on Canary, file new bugs.
Project Member

Comment 20 by bugdroid1@chromium.org, Dec 1 2017

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/8f0e7748d905b50d30e4d6f92c3a5aed58a888c4

commit 8f0e7748d905b50d30e4d6f92c3a5aed58a888c4
Author: pdfium-deps-roller@chromium.org <pdfium-deps-roller@chromium.org>
Date: Fri Dec 01 00:40:28 2017

Roll src/third_party/pdfium/ fee910e6f..1980f10ff (15 commits)

https://pdfium.googlesource.com/pdfium.git/+log/fee910e6f81f..1980f10ff2b8

$ git log fee910e6f..1980f10ff --date=short --no-merges --format='%ad %ae %s'
2017-11-30 dsinclair Simplify XDP parsing code
2017-11-30 dsinclair Rename XFA_ATTRIBUTEENUM to XFA_AttributeEnum enum class
2017-11-30 dsinclair Move packet information into simple parser
2017-11-30 dsinclair Make parsers work off XFA_PacketType enum
2017-11-30 dsinclair A CXFA_Node can only be in one packet
2017-11-30 dsinclair Cleanup XFA packet code
2017-11-30 rharrison Rewrite lower level details of extracting text from page
2017-11-30 dsinclair Create CXFA_Node::NameToAttributeEnum
2017-11-30 dsinclair Move setting of XML content back to specific set methods
2017-11-30 dsinclair Rename GetAttributeEnumById to CXFA_Node::AttributeEnumToName
2017-11-30 dsinclair Remove the packets from attribute data.
2017-11-30 dsinclair Generate XFA node attribute information
2017-11-30 thestig Fix GBK2K-H CMap usage.
2017-11-30 thestig Use initializer list in CPDF_DataAvail ctor.
2017-11-30 thestig Relax checks in CFX_FaceCache::LoadGlyphPath().

Created with:
  roll-dep src/third_party/pdfium
BUG= 654578 , 788864 


The AutoRoll server is located here: https://pdfium-roll.skia.org

Documentation for the AutoRoller is here:
https://skia.googlesource.com/buildbot/+/master/autoroll/README.md

If the roll is causing failures, please contact the current sheriff, who should
be CC'd on the roll, and stop the roller if necessary.


TBR=dsinclair@chromium.org

Change-Id: Ic87fbd3ca5dbec12418aa60db84ae9e894431881
Reviewed-on: https://chromium-review.googlesource.com/802188
Reviewed-by: <pdfium-deps-roller@chromium.org>
Commit-Queue: <pdfium-deps-roller@chromium.org>
Cr-Commit-Position: refs/heads/master@{#520774}
[modify] https://crrev.com/8f0e7748d905b50d30e4d6f92c3a5aed58a888c4/DEPS

Sign in to add a comment