New issue
Advanced search Search tips

Issue 604587 link

Starred by 4 users

Issue metadata

Status: Fixed
Owner:
Closed: Jun 2016
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Windows
Pri: 3
Type: Bug



Sign in to add a comment

Printing to a debug build cloud print proxy results in abort/retry/ignore error

Project Member Reported by thestig@chromium.org, Apr 19 2016

Issue description

Version: r388121 ToT
OS: Windows

What steps will reproduce the problem?
(1) Run Chrome, or Chromium with API keys and --enable-cloud-print-proxy
(2) Go to chrome://devices
(3) Click Add printers
(4) Complete the cloud printer proxy set up.
(5) Go to a webpage
(6) Try to print the webpage to a newly added printer

What is the expected output?

Using the built-in XPS virtual printer as an example - a dialog pops up to ask for a file name. Shortly after, the .xps file with that name appears and it contains the print out.

What do you see instead?

Using the built-in XPS virtual printer as an example - a dialog pops up to ask for a file name. Shortly after, the .xps file appears without the print out. An abort/retry/ignore dialog pops up.
 
I've started bisecting, but it may be hard with pre-built Chrome binaries due to  bug 604106 , which prevents step 4 from completing. Chromium snapshots do not work for bisecting.

Currently I have:

51.0.2665.0 / 378647 - good
51.0.2666.0 / 379069 - presumably bad due to r378704 which triggers this bug
51.0.2686.0 / 382218 - bad
Labels: M-51
Blocking: 602736
Well, my local debug build at 378647 is bad too, so I wasted some time bisecting today. Sometimes it takes a few print jobs to repro. :\
Cc: wfh@chromium.org
Labels: -Pri-1 -Type-Bug-Regression -M-51 Pri-3 Type-Bug
Owner: ----
Status: Available (was: Untriaged)
Summary: Printing to a debug build cloud print proxy results in abort/retry/ignore error (was: Printing to a cloud print proxy results in abort/retry/ignore error)
It seems to only happen if the service process is from a debug build. Canary seems to work fine.

Lowering priority, +wfh for reinforcement.
Blocking: -602736
Owner: thestig@chromium.org
Can you provide a quick update on this issue?
Still happening, even for regular print to XPS. No idea why.
Just to confirm, this only occurs with a debug build, and is not out in the wild (or in  Canary)?  
Cc: -wfh@chromium.org tsepez@chromium.org jochen@chromium.org
Components: -Services>CloudPrint Internals>Printing
Sometimes it takes a couple tries to reproduce. It seems to happen when printing, period.

When I run with --no-sandbox, I get more details:

fxjs_v8.cpp / line 158 / g_isolate == pIsolate.
It looks like we are calling chrome_pdf::InitializeSDK() / chrome_pdf::ShutdownSDK() / chrome_pdf::InitializeSDK(), and it fails the second time inside InitializeSDK() -> FPDF_InitLibraryWithConfig() -> IJS_Runtime::Initialize() -> FXJS_Initialize().

I suspect ShutdownSDK() should somehow call FXJS_Release(), but isn't doing that right now.
Project Member

Comment 13 by bugdroid1@chromium.org, Jun 29 2016

Status: Fixed (was: Available)
Cc: amistry@chromium.org thestig@chromium.org dsinclair@chromium.org
 Issue 622179  has been merged into this issue.

Sign in to add a comment