New issue
Advanced search Search tips

Issue 716447 link

Starred by 1 user
Status: Archived
Owner:
thestig@chromium.org
Closed: Aug 2017
Components:
EstimatedDays: ----
NextAction: ----
OS: Windows
Pri: 2
Type: Bug



Sign in to add a comment

Printing from a web page is extremely slow

Project Member Reported by pastarmovj@chromium.org, Apr 28 2017 
After upgrading to Chrome 57.0.2987.133, printing receipts from a web page is extremely slow; often taking as long as 3 minutes.  To troubleshoot, I have done the following:
1. Delete Cookies, history, cache, etc
2. Tried in incognito window
3. Scanned computer for viruses, etc
4. Launched web page in other browsers and noted NO issues printing the same receipt

Copied from: https://productforums.google.com/forum/#!topic/chrome-admins/R0PF62WZ0_M;context-place=forum/chrome-admins

Comment 1 by thestig@chromium.org, Apr 28 2017

Labels: Needs-Feedback
We need more information here:

1) What OS is this on? e.g. Window 10?
2) Is there a sample receipt that you can share?
3) What printer model / driver version are you trying to print to?
4) Is the printer directly attached via USB, or some kind of network / cloud printer?

Comment 2 by cw...@tlcdelivers.com, May 16 2017 

1.) Windows 10 and 7 (pro)
2.) no
3.) Various - Epson TM-U220
4.) USB

I apologize for the delayed response.  For some reason I did not get or see the notification of comment.  I noticed that an update has been released.  I am looking to see if printing speeds have improved but it will take me some time to test.

Comment 3 by thestig@chromium.org, May 19 2017

Components: Internals>Printing
Labels: OS-Windows
Are you using the --kiosk-printing command line flag by any chance? We have a report about slow printing in bug 706180 as well.

Comment 4 by thestig@chromium.org, May 19 2017 

Can you also try out Google Chrome Canary and see if the the bug manifests there?

Comment 5 by thestig@chromium.org, Aug 8 2017

Status: Archived (was: Untriaged)
2+ months without feedback. Please let us know if you have an update on this bug.
►

Sign in to add a comment