Verified the issue on Latest Stable# 52.0.2743.116 on Windows and could not reproduce the issue.
@billsamuel -- Could you please update your Chrome to latest version mentioned and provide us the update.
Thanks in Advance.

Updated to that version. Tried printing from Chrome. Exact same problem. New version does not fix.

a) What printer(s) have you tried printing to?
b) If you select "Save as PDF" as the destination, does the saved PDF have the same problem?
b1) When you said "printing to PDF" - is that the same as "Save as PDF" or something else?
c) If you go to a friend's computer and try it there, can you reproduce the problem? If you cannot, you can see why this is rather hard to track down.

a) An HP LaserJet 1320 and an Epson WorkForce 845.
b) Yes, which confirms for me that it is not a printer issue.
b1) Selecting as printer either Microsoft Print to PDF or Primo PDF.
c) I tried in the computer room of my retirement community, and it worked fine there.

This does not happen with other browsers (I also have IE & Firefox) or any other program. The only other printing problem I have is with Nitro PDF, which Nitro has acknowledged is a problem with their compatibility with the current build of Windows 10 which applies to all users. This is why I am convinced it is a Google Chrome problem. And there is nothing particularly unusual about my configuration of which I am aware. But Chrome, and only Chrome, has problems with it.

Can you attach the output from (b) here? i.e. The "Save as PDF" generated PDF, and not the PDFs from other PDF generators.

Your answer to (c) means there is something wrong in particular with this computer and it's probably not a widespread problem. Have you tried disabling all browser extensions on the affected computer? Given it's Windows, could there be malware?

What do you mean by "Save as PDF" - there's no built-in option for that in Chrome.

Oh, then we are not on the same page here with comment 4 and 5. In comment 4, question (b) is referring to Chrome's built in ability to print to PDF, without going through a PDF virtual printer. It looks like this: http://cdn.ghacks.net/wp-content/uploads/2012/10/chrome-save-as-pdf.jpg and it is a feature that has been in Chrome's print preview dialog for years.

So one more question - are you using print preview, or the native print dialog? If you attach some screenshots of what your print dialog looks like, that can be helpful.

I tried disabling all extensions. Still have same problem.

Did MalwareBytes scan. No Malware found.

Thanks for telling me about Save as PDF. There is no indication that is a Chrome feature and it's not available except through a print dialog. So essentially it's a hidden feature that you need someone to tell you about as you did. Not sure why Google does that.

The problem does not exist with Save as PDF. It exists with all other printer options. That should not be the only way to print properly. You should be able to print directly to a printer without having to save as a file first. You can in other browsers. You used to be able to do so in Chrome.

Many products have features that may or may not be obvious. We thought it is obvious because it shows up on the list of destinations whenever one tries to change the printer. Glad you found Save as PDF eventually.

I agree that "Save as PDF" should not be the only way to print. The problem here is there is something wrong with your PC, and we have no idea what it is. As you can see with (c) above, other PCs don't have this problem. It's likely 99.99% of PCs don't have this problem, because this is the first time I have heard of this issue.

It would be helpful if you take a web page, and print it thrice:
- Once with Save as PDF as the destination
- Again with either Microsoft Print to PDF or Primo PDF as the destination
- One more time with "Microsoft XPS Document Writer" as the destination

Attach the 3 generated .pdf / .xps files to this bug, and we will examine the output and see what we find. Maybe the output can give us some clue as to what is going wrong.

Here is a test Web page the 3 ways requested. I misspelled 2 of the file names.

Deleted: Test - Save as PDF - 20160809.pdf 2.5 MB

Test - Save as PDF - 20160809.pdf 2.5 MB Download

Deleted: Test - Priom PDF - 20160809.pdf 393 KB

Test - Priom PDF - 20160809.pdf 393 KB Download

Deleted: Test - Microsoft XPX - 20160809.oxps 317 KB

Test - Microsoft XPX - 20160809.oxps 317 KB Download

Thanks for the print outs. One more question - has this problem always existed on this computer, or did it suddenly start recently? If it started recently, when?

+halcanary to maybe help take a look. One interesting comparison is the text on page 1 disappears about half way down, but the picture of Hillary does not get cut off.

No, it used to be fine. This started happening maybe 2-3 weeks ago.

That's interesting. I wonder what changed. The next test is a bit tedious, but it can help us determine if Chrome is at fault, or something else on the computer is broken.

Here are 3 different versions of Chromium in the links at the bottom. It's Chrome like, but with a blue icon. The build numbers are 386255, 394937, and 410620, respectively. Trying the older builds let us "go back in time" to simulate Chrome from before.

For each build:
- Download the mini_installer.exe.
- It might get renamed to WinSomeGibberish_mini_installer.exe.
- Double click the icon to install it.
- And after a little bit of time, a blue Chromium icon should appear on the Windows desktop. Chromium may also auto-launch it self. If not, double click the Chromium icon to start it.
- In Chromium, try printing to Primo PDF, and write down whether the print out was good or not.
- Then quit Chromium, and go to Control Panel -> Programs and Features, and uninstall Chromium.

Then repeat the process for the next two builds. Hopefully the process will become easier after the first time.

https://commondatastorage.googleapis.com/chromium-browser-snapshots/index.html?prefix=Win/386255/
https://commondatastorage.googleapis.com/chromium-browser-snapshots/index.html?prefix=Win/394937/
https://commondatastorage.googleapis.com/chromium-browser-snapshots/index.html?prefix=Win/410620/

386255 and 394937 had the same problem, but 410620 printed OK.

Someone in the Google Help Forum reported he has had the problem, and discovered it was associated with the laptop lid being closed. I am using a laptop with an external monitor with a different resolution. When I tried printing with the laptop lid open, indeed it did work fine. Don't know what in the Chrome current and some past builds' code results in that, but that is the circumstance which causes the problem with Chrome. No other application, including other browsers, acts this way, so it is something unique with the Chrome code. And the code for Build 410620 did not contain the problem code string.

Thanks for the hint. Will look into this a bit more. The good news is that if 410620 printed ok with the laptop lid closed, and 394937 has the problem, then that means a newer version of Chrome will eventually have the fix. What we should do is try to find the fix and try to fast-track it users.

+scottmg,robliao to see if they have heard of this and know what the fix is.

I haven't heard about this. My initial thought is maybe the margins are set incorrectly. The first file on page 1 has some interesting text issues at the end of the printed region. Was it like that in the page too?

For some reason, the files in Comment 12 don't download for me: "Failed - Server problem". 

(re: download @12, crbug is being flaky at the moment)

I don't know of anything other than filing a similar-ish bug here https://bugs.chromium.org/p/chromium/issues/detail?id=566248 a while back. But I sadly am not aware of any fix. That one seems like it might be timing related.

I tried build 386255 on a Windows 7 laptop that has a resolution of 1600x900 + a monitor that's 1920x1200. Couldn't repro with Wikipedia and the Washington Post. Using the virtual XPS Document Printer.

- I tried closing the lid, and then plugging in the monitor.
- I also tried starting the laptop with the monitor plugged in. In this case, both monitors were 1440x900. When I closed the lid, the monitor went to its native resolution.

I'll try again with a Windows 10 laptop when I find one.

I failed to find a Windows 10 laptop today. If you don't want to wait for me, you can try some builds on https://commondatastorage.googleapis.com/chromium-browser-snapshots/index.html?prefix=Win/ between 394937 and 410620 to narrow it down.

Now it's gotten worse. The same problem now occurs when I'm doing it with
the laptop open, and with Save as PDF, both of which used to work. There is
no longer any way at all to print from Chrome.



Bill Samuel
phone: 240-477-8827
mobile: 301-943-6406
address: 701 King Farm Blvd., Apt. 134, Rockville, MD 20850-6168
email: billsamuel3@gmail.com
<https://www.facebook.com/bill.samuel>  <https://twitter.com/billsamuel>
<https://www.linkedin.com/in/billsamuel>

Get a signature like this! <https://newoldstamp.com/editor/>

Bill, as I mentioned in comment 22 - can you try some more builds like you did in comment 16 to narrow down the range where Chromium builds started to work well for you again?

Also, can you attach a bad "Save as PDF" PDF?

The "Save as PDF" PDFs are good. See comment 10.

I was looking at comment 23.

Hi team,

We've received a new report from an Enterprise account being affected by this problem. I'll provide more details on his scenario:

* Chrome browser version 53.0.2785.116.
* Issue reproducible on different OS versions, which are Windows 8.1 pro and Windows 10 64 bit pro.
* Print preview shows fine, so we can say that the PDF is rendered correctly during the preview , but the print output in paper prints with around %20 percent of the bottom print cropped off.
* Printing the document using the Windows print dialog has the same result.
* Issue started approximately a month ago. No confirmation which was the version where it corrupted, but from this bug report I see that it was reported in M51.
* The Chrome PDF viewer plugin is the latest one. 
* Issue is consistent regardless of the printer.
* Printer proprietary drivers are in use, and those have been updated to their latest version.
* Issue is isolated to Chrome only, and happens regardless of the website. They print from Google Services mostly.

Let me know if you need additional info. I’m not posting the example PDFs, since the ones he shared with Tech Support may contain sensitive data from their side.

hernandezma: Have you been able to reproduce this problem personally? If you can work with your Enterprise customer to figure out how, that would be helpful.

thestig: Unfortunately, I wasn't able to reproduce this issue on site. I tried to, but seems like there's something else behind that's causing this in the OS, since it's not reproducible in the given OS/browser version. If there's additional info that'll help in this investigation, please let me know.

For me, and I believe most reporting the issue, the problem occurs when you have a laptop connected to an external monitor, and the resolution of the laptop screen and the external monitor are different. The Enterprise report may be a different circumstance than those of us who have reported it on our personal PCs. That would have to be teased out with more information from the enterprise which reported the problem.

This is browser-specific problem which exists with the current build but not with all past builds. Other browsers do not have the problem, and the problem is not specific to a particular OS.

Bill, can be you specific about what the resolution of the laptop screen and external monitor are?

Laptop 2560x1440
External 1920x1200

Just using defaults for both

I can reproduce this issue and have provided output samples and Chrome logs to support.  We are an enterprise customer with ~1000 users impacted. If I can contribute further please let me know.

We are also running into this issue. We are an enterprise customer with ~1,000 users also. In some cases we can reproduce and others are sporadic.

We are using Lenovo Yoga 260 devices with the OneLink+ Dock (MT: 40A4) to connect to VGA displays.
Chrome version 53.0.2785.116m (64-bit) and Canary Version 55.0.2868.0 canary (64-bit)y 

Sample 1: 1920x1080 int and 1280x1024 ext
Sample 2: 1600x900 ext
Sample 3: 1280x1024 ext

Sample portriat output attached

Deleted: 3651_001.pdf 201 KB

3651_001.pdf 201 KB Download

Screen shot of print preview window attached

Deleted: Capture.PNG 281 KB

	Capture.PNG 281 KB View Download

Sample horizontal output and print preview attached.
Note: Not a clear "cut off"

Deleted: 3655_001.pdf 126 KB

3655_001.pdf 126 KB Download

Deleted: CaptureH.PNG 108 KB

	CaptureH.PNG 108 KB View Download

The good news is we reproduced the problem on a Windows 10 laptop connected to an external monitor. The not as good news is we need some time work out why this is happening. Stay tuned!

robliao: rbpotter bisected and says r407508 is when this problem went away.

I believe that means on Chrome 53, running Chrome with --enable-per-monitor-dpi should make this problem go away. In Chrome 54, the problem will just go away on its own.

The quick and dirty solution I've found is to sign out of the account and sign back in after the laptop has been hooked up to an external monitor. I noticed that when I went into the display settings. It had a message that said some of the programs would not respond correctly until you sign out. After giving that a shot I couldn't get it to reproduce the error until I disconnected the laptop and powered it off and left it over night and then reconnected it to the dock. 

Some things I found after trying it with different display cords.

VGA - laptop open prints fine. Closed, half page.
DVI - laptop open half page. Closed, half page.
HDMI - laptop open half page. Closed, half page.
Display Port - laptop open half page. Closed, half page.

each time it printed half page in the display settings there was a prompt to sign out so that settings could be reloaded or something. 

the only exception was with VGA with the laptop open. There was no need to reload then. 

If ya'll haven't already figured this out I hope the info helps. 

That seems rather surprising to me. I would not have expected per-monitor DPI to address this situation.

Slight correction there was no need to sign out when it was connected to VGA and the display was open. If the display is closed the monitor readjusts and the settings need to be reloaded by signing out. Hope that clarifies it. 

I have found that when docked, if you pull the Chrome window over to the Native Screen (The laptop or surface screen in our case) that it prints fine. Only prints half a page when the Chrome window is on the external screen.

re: comment 50, comment 51 - So have you tried Chrome 53 with --enable-per-monitor-dpi, or Chrome 54+ to see if the problem still exists?

Is there a way to update to Chrome 54 other than via Canary?

You can install Chrome beta channel over Chrome stable channel, and that will upgrade you to Chrome 54. Though in the upcoming week or two, Chrome 54 will be promoted to stable channel and Chrome 55 to beta. So you can also just wait and see.

Chrome 54 is now shipping on the stable channel, I'll let you know if I hear anything.

So Chrome 54 has been fully pushed out to stable. Has the situation improved?

Yes, this update seems to have resolved the issue.
THANK YOU for your help in getting this taken care of!!!

You are welcome. Glad it's working for you. I heard similar reports from another group of affected users. Closing the bug and crediting Rob.

Yes, the latest release of Chrome does seem to have fixed the problem.