additional information.
It is one of the preconditions that the printer is set up.

1) Did it work before with previous version of Chrome?
2) What print driver are you using with your Ricoh printer?
3) Can you translate the error message to English?

1) Did it work before with previous version of Chrome?

 It operates normally in the previous version.
 58.0.3029.110 (64-bit)

2) What print driver are you using with your Ricoh printer?

 I uploaded a file.　
 ※183230.exe

3) Can you translate the error message to English?

 I uploaded a file.
 ※I can not print in Chrome.ppt

Deleted: I can not print in Chrome.ppt 628 KB

I can not print in Chrome.ppt 628 KB Download

Deleted: 183230.exe 15.4 MB

183230.exe 15.4 MB Download

Thank you for providing more feedback. Adding requester "thestig@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 attached 1832300.exe file is the same as the file one can download from: http://support.ricoh.com/bbv2/html/dr_ut_d/new/history/w/bb/pub_j/dr_ut_d/4101028/4101028137/V2100/5183230/183230/history.htm

As a quick workaround, can you check and see if there is a non-RPCS driver available for your printer? For example, a PostScript or PCL driver.

To be specific, if there exists an alternative PostScript or PCL driver for your printer, can you try uninstalling the RPCS driver, and install the alternative driver instead? I think that is the fastest way to get printing working again, while we investigate this issue.

To explain the situation, there are printer drivers that are incompatible with Windows 10. Trying to print from Chrome results in the entire browser crashing, which is a bad experience. To prevent this, we are trying to detect the incompatible printer drivers to avoid the crash. Instead, of crashing, trying to print with an incompatible print driver results in an error message in print preview.

Ricoh's English RPCS drivers do not work with Windows 10. In fact, Ricoh's English website does not offer the RPCS drivers for download anymore. So we used the type of printer driver as a heuristic, and we blacklisted all RPCS drivers. We did not know Ricoh's Japanese RPCS drivers are in fact, compatible with Windows 10.

Last week, we were looking at another incompatible printer driver, for which we have an alternate way of detecting the incompatibility. That works for the Ricoh English RPCS driver as well. So what we can do is remove the check for RPCS drivers altogether.

According to the URL, Japan Ricoh supports RPCS for Winodws 10.
So uncheck the RPCS driver.

http://www.ricoh.co.jp/support/os/info/winend_info.html

Can I understand that the problem of this crash is resolved by unchecking the RPCS driver on Chrome side?

Yes, that is what we plan to do, but it takes time. If you cannot wait, please consider using an alternate print driver as a workaround.

To be clear, I don't think the problem you are experiencing is a crash. It's just the browser does not want to print to any RPCS printers on Windows 8 or 10. You can still cancel print preview and continue using Chrome.

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

commit 685631bcd8b90950498e80f74009660ea5f75010
Author: rbpotter <rbpotter@chromium.org>
Date: Fri Jun 09 02:48:52 2017

Printing: Remove check for Windows RPCS printers

Now that we check for invalid paper sizes, we no longer need the RPCS
driver check to prevent crashes on Win10. This will also fix breakage
of Japanese RPCS drivers that support Win10.

BUG= 730919 

Review-Url: https://codereview.chromium.org/2932043002
Cr-Commit-Position: refs/heads/master@{#478172}

[modify] https://crrev.com/685631bcd8b90950498e80f74009660ea5f75010/printing/backend/win_helper.cc

Do you know the date when this fix is ​​reflected in the stable version?

If we do not take any more actions, then in about 3 months with Chrome 61 according to https://www.chromium.org/developers/calendar, but we need to decide if we want to expedite that. Stay tuned.

+soushi FYI

We use Chrome as the main browser of the business system.
We are in great trouble and there are no alternatives.
I heard from Softbank that requests from other companies in Japan are increasing.
I hope to release it as a virgin 59 patch as soon as possible.
I expect it!

I would recommend having someone in the company's IT department use Google Chrome on the beta or dev channel, so they can detect these issues earlier before it reaches stable channel. There's also our Chrome for Business help center, which has articles on how to best deploy Chrome and other topics that may be of interest: https://support.google.com/chrome/a/#topic=4386754

Release managers: My recommendation for minimizing risk on the M59 and M60 branches is to revert r455789 for  bug 679160 . The only negative effect is those with Ricoh printers and English RPCS drivers on Windows 8+ will suffer crashes, just like they did before with M58. We'll let the current solution bake on M61. It can't be cleanly merged to M59 / M60 anyway.

Requesting to revert r455789 on M59.

thestig@ - please confirm if this a safe merge overall? If it's safe, I am fine with merging to M59. 

It should be safe to revert. If we want to be even safer, we can just revert the modifications to printing/backend/win_helper.cc in that CL. The C++ and JS changes in the CL are actually independent.

+dpapad to confirm.

The JS changes in r455789 indeed seem independent from the change to the printing backend.

So updating the request: Only revert the printing/backend/win_helper.cc changes in r455789.

Approving merge for M59. 

Thank you for the merge to 59.
We want you to tell us what day it will be reflected.

I forgot to write down the bug number when merging: https://chromium.googlesource.com/chromium/src/+/d543d483e3b9816e0b34e69523107756a911437c

For Chrome stable, revision 59.0.3071.100 and newer should work again. I do not know when the next stable update will be release though.

Thanks for providing the information.
I am looking forward to being reflected.

We confirmed that it can reflect and print in the following version.
61.0.3127.0（Official Build）canary （64 ビット）

I am waiting for implementation to the stable version.

Unable to verify this issue as we don't have any machine installed with the specific RPCS driver with us. Hence adding the Verified label as per comment #27.

Thanks!!!!

I've verified on my test machine:
OS Name:    Microsoft Windows Server 2012 R2 Datacenter
OS Version: 6.3.9600 N/A Build 9600

Google Chrome	61.0.3129.0 (Official Build) canary (64-bit) (cohort: 64-Bit)
Revision	b7e12bae8572c1ed03d0959ed71df8e4efe2f8ee-refs/heads/master@{#478840}

with the driver: ricoh RPCS basic color Ver 3.4.0.0

We should also merge to M60.

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

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

known regression, approving merge to M60. 

M60 merge: https://chromium.googlesource.com/chromium/src/+/2bdbdbda1da6d7f48657a07897f00b3dbd98383d

Users with Chrome 59 should be updating to 59.0.3071.104. Please let us know if the issue is fixed with the latest update.

I confirmed that the problem was solved with the stable version.
※59.0.3071.104

Thanks for the update!