Issue 426858 in chromium: Launching Google Chrome 38 in background using node and socket-io

[chro...@googlecode.com]

Status: Unconfirmed
Owner: ----
Labels: Pri-2 Via-Wizard Type-Bug-Regression OS-Windows

New issue 426858 by rinat.us...@gmail.com: Launching Google Chrome 38 in
background using node and socket-io
https://code.google.com/p/chromium/issues/detail?id=426858

UserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_9_5)
AppleWebKit/537.36 (KHTML, like Gecko) Chrome/38.0.2125.104 Safari/537.36

Steps to reproduce the problem:
1. Launch chrome using sockets in the background with service that will be
using AD user to run nodejs in the background
2.
3.

What is the expected behavior?
Windows service is running node.js and i'm launching Chrome by request via
Socket-io. Chrome should open selected page and once page is fully loaded,
socket should close it.

What went wrong?
Service opens Chrome and closes it right away and chrome is not even able
to load requested page. Problem persists only if i run node in background
using service.

I also noticed that for each open instance of Chrome there is one instance
of rundll32.exe (chrome is using it for flash). And rundll32.exe instances
are persistent and looks like they are crashing chrome. i dont see any
rundll32.exe when I run node and launch chrome in foreground.

Did this work before? Yes I worked with chrome 37, before i upgraded to 38

Chrome version: 38.0.2125.104 Channel: stable
OS Version: Server 2008 SP2
Flash Version: Shockwave Flash 15.0 r0

set node to launch chrome with --enable-logging --v=1 And saw these errors
(not sure if related):

[1844:1872:1023/153655:ERROR:gpu_process_transport_factory.cc(418)] Failed
to establish GPU channel.
[1844:1872:1023/153655:ERROR:child_process_launcher.cc(344)] Failed to
launch child process
[1844:1872:1023/153655:ERROR:child_process_launcher.cc(344)] Failed to
launch child process
[1844:1872:1023/153655:ERROR:child_process_launcher.cc(344)] Failed to
launch child process
[1844:1872:1023/153655:ERROR:child_process_launcher.cc(344)] Failed to
launch child process
[1844:1872:1023/153655:ERROR:child_process_launcher.cc(344)] Failed to
launch child process
[1844:1872:1023/153655:ERROR:child_process_launcher.cc(344)] Failed to
launch child process
[1844:1872:1023/153655:ERROR:child_process_launcher.cc(344)] Failed to
launch child process
[1844:1872:1023/153655:ERROR:child_process_launcher.cc(344)] Failed to
launch child process
[1844:1872:1023/153655:ERROR:child_process_launcher.cc(344)] Failed to
launch child process
[1844:1872:1023/153655:ERROR:child_process_launcher.cc(344)] Failed to
launch child process
[1844:1872:1023/153655:ERROR:child_process_launcher.cc(344)] Failed to
launch child process
[1844:3408:1023/153656:VERBOSE1:ssl_client_socket_nss.cc(3477)] CT
Verification complete: result -158 Invalid scts: 0 Verified scts: 0 scts
from unknown logs: 0
[1844:3408:1023/153656:ERROR:child_process_launcher.cc(344)] Failed to
launch child process
[1844:3408:1023/153701:VERBOSE1:bandwidth_metrics.h(95)] Bandwidth:
294975Kbps (avg 294975Kbps)
[1844:3408:1023/153723:VERBOSE1:ssl_client_socket_nss.cc(3477)] CT
Verification complete: result -158 Invalid scts: 0 Verified scts: 0 scts
from unknown logs: 0

--
You received this message because this project is configured to send all
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings

[chro...@googlecode.com]

Comment #1 on issue 426858 by rinat.us...@gmail.com: Launching Google

Chrome 38 in background using node and socket-io
https://code.google.com/p/chromium/issues/detail?id=426858

Something is definitely wrong with latest version of chrome running in the
background. And seems like the only fix is to downgrade it to 37.

Also here is a question i posted on superuser.com

http://superuser.com/questions/830269/launching-google-chrome-38-in-background-using-node-and-socket-io

[chro...@googlecode.com]

Comment #2 on issue 426858 by luke.a.p...@gmail.com: Launching Google

Chrome 38 in background using node and socket-io
https://code.google.com/p/chromium/issues/detail?id=426858

We launch in the background and run tests and this bug means we cannot run
tests against the latest version of the chrome. Please fix or provide
work-around.

[chro...@googlecode.com]

Comment #3 on issue 426858 by luke.a.p...@gmail.com: Launching Google

Chrome 38 in background using node and socket-io
https://code.google.com/p/chromium/issues/detail?id=426858

I get this with v38

browser #1 <stderr>:
[3856:9316:1028/121322:ERROR:google_update_settings.cc(288)] Failed opening
key
Software\Google\Update\ClientStateMedium\{4DC8B4CA-1BDA-483e-B5FA-D3C12E15B62D}
to set usagestats; result: 5
browser #1 <stderr>:
[3856:8448:1028/121323:ERROR:gpu_process_transport_factory.cc(418)] Failed
to establish GPU channel.
browser #1 <stderr>:
[3856:8448:1028/121323:ERROR:child_process_launcher.cc(344)] Failed to
launch child process
**FAIL**

and with V37

browser #1 <stderr>:
[6556:8372:1027/145942:ERROR:gpu_info_collector_win.cc(103)] Can't retrieve
a valid WinSAT assessment.
browser #1 <stderr>:
[6556:9428:1027/145942:ERROR:google_update_settings.cc(290)] Failed opening
key
Software\Google\Update\ClientStateMedium\{4DC8B4CA-1BDA-483e-B5FA-D3C12E15B62D}
to set usagestats; result: 5
browser #1 <stderr>:
[6556:8372:1027/145942:ERROR:gpu_process_transport_factory.cc(402)] Failed
to establish GPU channel.
**SUCCESS**

[chro...@googlecode.com]

Updates:
Labels: TE-NeedsTriageFromMTV

Comment #4 on issue 426858 by msrchan...@chromium.org: Launching Google

Chrome 38 in background using node and socket-io
https://code.google.com/p/chromium/issues/detail?id=426858

(No comment was entered for this change.)

[chro...@googlecode.com]

Comment #5 on issue 426858 by rstarke...@gmail.com: Launching Google Chrome

38 in background using node and socket-io
https://code.google.com/p/chromium/issues/detail?id=426858

This is also affecting our automated testing.
We invoke chrome from a windows batch script in a Jenkins post build step.
Chrome normally opens the test page, which executes unit tests and
automatically dumps them out to the download directory.

I see similar output as follows:
C:\Jenkins\jobs\***\workspace>./batch/ChromeUnitTestRunner.bat
Running tests for page \workspace\samples\02\unitTests\tests.html
[5284:1320:1105/104533:ERROR:gpu_info_collector_win.cc(145)] Could not read
gaming score from assessment results.
[5284:1320:1105/104533:ERROR:child_process_launcher.cc(344)] Failed to
launch child process
[5284:1320:1105/104533:ERROR:child_process_launcher.cc(344)] Failed to
launch child process
[5284:1320:1105/104533:ERROR:child_process_launcher.cc(344)] Failed to
launch child process
[5284:1320:1105/104533:ERROR:child_process_launcher.cc(344)] Failed to
launch child process
[5284:1320:1105/104533:ERROR:child_process_launcher.cc(344)] Failed to
launch child process
[5284:1320:1105/104533:ERROR:child_process_launcher.cc(344)] Failed to
launch child process
[5284:8188:1105/104538:ERROR:child_process_launcher.cc(344)] Failed to
launch child process
[5284:8188:1105/104633:ERROR:child_process_launcher.cc(344)] Failed to
launch child process

If it helps, we are running on a virtual machine hosted on a server rack,
without a native GPU.

[chro...@googlecode.com]

Comment #6 on issue 426858 by onno.van...@onknows.com: Launching Google

Chrome 38 in background using node and socket-io
https://code.google.com/p/chromium/issues/detail?id=426858

Same here. Out automated testing no longer works. In chrome_debug.log I see
[5524:10384:1107/113727:ERROR:gpu_process_transport_factory.cc(418)] Failed
to establish GPU channel.
[5524:10384:1107/113727:ERROR:child_process_launcher.cc(344)] Failed to
launch child process
[5524:10384:1107/113727:ERROR:child_process_launcher.cc(344)] Failed to
launch child process
[5524:10384:1107/113727:ERROR:child_process_launcher.cc(344)] Failed to
launch child process
[5524:10384:1107/113727:ERROR:child_process_launcher.cc(344)] Failed to
launch child process
[5524:10384:1107/113727:ERROR:child_process_launcher.cc(344)] Failed to
launch child process
[5524:10384:1107/113727:ERROR:child_process_launcher.cc(344)] Failed to
launch child process
[5524:10384:1107/113727:ERROR:child_process_launcher.cc(344)] Failed to
launch child process

Is it possible to downgrade to a release that works. I am using Chrome 38.
But I don't think it is possible to get an older version of Chrome.