New issue
Advanced search Search tips

Issue 640396 link

Starred by 1 user
Status: Duplicate
Merged: issue 553446
Owner:
thestig@chromium.org
Closed: Aug 2016
Cc:
scottmg@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Windows
Pri: 2
Type: Bug-Regression



Sign in to add a comment

Windows print spool can get stuck

Project Member Reported by thestig@chromium.org, Aug 23 2016 
Version: r272250 onwards
OS: Win 7

What steps will reproduce the problem?
(1) Install the "HP LaserJet 4L/4ML PostScript" printer driver on the FILE: port
(2) Open the printer job queue
(3) Load https://en.wikipedia.org/wiki/Phobos_(moon)
(4) Press ctrl + shift + p to print with the native print dialog - print all pages, save as c:\test\1.ps
(5) Repeat (4), but save as c:\test\2.ps
(6) Repeat (5), but only print page 2, and save as c:\test\3.ps

What is the expected output?

In (6), the print job should exit the "spooling" state in the printer job queue. c:\test\3.ps should be non-zero in size.

What do you see instead?

In (6), the print job is stuck in the "spooling" state in the printer job queue until Chromium exits. c:\test\3.ps is zero in size.

Comment 1 by scottmg@chromium.org, Aug 23 2016 

I couldn't repro exactly... though I couldn't find that exact driver on Win10,  so I tried installing "HP LaserJet 4200/4300 PCL6 Class Driver".

With that on Canary, it printed OK each time, but if the print job was still spooling when I tried to print the next one, it just closed the print dialog after clicking "Print" (and had no effect). If the job was done, it printed as expected.

Comment 2 by thestig@chromium.org, Aug 23 2016 

I'm waiting for each job to finish before starting the next. Since I have a reliable repro, I'll fix it. I used a PS printer driver just so it's easy to examine the output.

Comment 3 by thestig@chromium.org, Aug 23 2016 

One side is saying "I printed page 1" and the other side is saying "Give me page number 2."

Comment 4 by thestig@chromium.org, Aug 24 2016

Mergedinto: 553446
Status: Duplicate (was: Assigned)
Maybe the original repro is a bit too elaborate and steps 4/5 can be skipped. Anyway, I realized this bug was already in my queue.
►

Sign in to add a comment