New issue
Advanced search Search tips

Issue 852715 link

Starred by 2 users
Status: Unconfirmed
Owner: ----
Cc:
vamshi.kommuri@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux
Pri: 2
Type: Bug-Regression



Sign in to add a comment

Getting a lot of errors and tab cannot be close when headless mode

Reported by masao.so...@gmail.com, Jun 14 2018 
UserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/67.0.3396.87 Safari/537.36

Steps to reproduce the problem:
1. Install stable version of google chrome, nodejs, nickjs and pm2
2. Run program with pm2.
program is in the other comments.
3. Access to nodejs by curl
4. pm2 monit
5. You can see lot of errors.
6. Also, I can not close tab by tab.close() that is from nickjs.

What is the expected behavior?
No error and tab should be closed.

What went wrong?
Here is error logs.
2018-06-13 14:37 : CHROME STDERR: [0613/143740.227105:ERROR:gpu_process_transport_factory.cc(1017)] Lost UI shared context.
2018-06-13 14:37 : CHROME STDERR: 
DevTools listening on ws://127.0.0.1:9222/devtools/browser/12f76570-7d3b-4426-8e42-6821ee7e440e
2018-06-13 14:37 : > It took 255ms to start and connect to Chrome (2 tries)
2018-06-13 14:37 : CHROME STDERR: [0613/143742.169722:ERROR:gles2_cmd_decoder.cc(3354)] ContextResult::kFatalFailure: fail_if_major_perf_caveat + swiftshader
2018-06-13 14:37 : CHROME STDERR: [0613/143742.172665:ERROR:gles2_cmd_decoder.cc(3354)] ContextResult::kFatalFailure: fail_if_major_perf_caveat + swiftshader
2018-06-13 14:37 : [info] MEO API started in development mode!
2018-06-13 14:40 : CHROME STDERR: [0613/144007.320494:ERROR:gpu_process_transport_factory.cc(1017)] Lost UI shared context.
2018-06-13 14:40 : CHROME STDERR: 
DevTools listening on ws://127.0.0.1:9222/devtools/browser/e2c7521b-85a0-4118-a5e8-d3bd607e8c0f
2018-06-13 14:40 : > It took 722ms to start and connect to Chrome (4 tries)
2018-06-13 14:40 : CHROME STDERR: [0613/144009.914110:ERROR:gles2_cmd_decoder.cc(3354)] ContextResult::kFatalFailure: fail_if_major_perf_caveat + swiftshader
2018-06-13 14:40 : CHROME STDERR: [0613/144009.916734:ERROR:gles2_cmd_decoder.cc(3354)] ContextResult::kFatalFailure: fail_if_major_perf_caveat + swiftshader
2018-06-13 14:40 : [info] MEO API started in development mode!
2018-06-13 14:40 : CHROME STDERR: [0613/144033.531034:ERROR:gpu_process_transport_factory.cc(1017)] Lost UI shared context.
2018-06-13 14:40 : CHROME STDERR: 
DevTools listening on ws://127.0.0.1:9222/devtools/browser/fe0b562e-ec43-49ee-b3e0-cc7565b42c7d
2018-06-13 14:40 : > It took 253ms to start and connect to Chrome (2 tries)
2018-06-13 14:40 : CHROME STDERR: [0613/144034.979060:ERROR:gles2_cmd_decoder.cc(3354)] ContextResult::kFatalFailure: fail_if_major_perf_caveat + swiftshader
2018-06-13 14:40 : CHROME STDERR: [0613/144034.981555:ERROR:gles2_cmd_decoder.cc(3354)] ContextResult::kFatalFailure: fail_if_major_perf_caveat + swiftshader
2018-06-13 14:40 : [info] MEO API started in development mode!
2018-06-13 14:44 : CHROME STDERR: [0613/144443.591714:ERROR:gpu_process_transport_factory.cc(1017)] Lost UI shared context.
2018-06-13 14:44 : CHROME STDERR: [0613/144443.597460:ERROR:socket_posix.cc(144)] bind() returned an error, errno=98: Address already in use (98)
2018-06-13 14:44 : CHROME STDERR: [0613/144443.597908:ERROR:socket_posix.cc(144)] bind() returned an error, errno=98: Address already in use (98)
2018-06-13 14:44 : CHROME STDERR: [0613/144443.598107:ERROR:devtools_http_handler.cc(292)] Cannot start http server for devtools. Stop devtools.
2018-06-13 14:44 : > It took 102ms to start and connect to Chrome (1 tries)
2018-06-13 14:44 : [info] MEO API started in development mode!
2018-06-13 14:45 : CHROME STDERR: [0613/144506.012671:ERROR:gpu_process_transport_factory.cc(1017)] Lost UI shared context.
2018-06-13 14:45 : CHROME STDERR: 
DevTools listening on ws://127.0.0.1:9222/devtools/browser/e7a898b0-4054-4d0f-baac-c4ab6bb012d3
2018-06-13 14:45 : > It took 253ms to start and connect to Chrome (2 tries)
2018-06-13 14:45 : CHROME STDERR: [0613/144507.913659:ERROR:gles2_cmd_decoder.cc(3354)] ContextResult::kFatalFailure: fail_if_major_perf_caveat + swiftshader
2018-06-13 14:45 : CHROME STDERR: [0613/144507.916606:ERROR:gles2_cmd_decoder.cc(3354)] ContextResult::kFatalFailure: fail_if_major_perf_caveat + swiftshader
2018-06-13 14:45 : [info] MEO API started in development mode!
2018-06-13 14:47 : > It took 102ms to start and connect to Chrome (1 tries)
2018-06-13 14:47 : CHROME STDERR: [0613/144724.027462:ERROR:gpu_process_transport_factory.cc(1017)] Lost UI shared context.
[0613/144724.034150:ERROR:socket_posix.cc(144)] bind() returned an error, errno=98: Address already in use (98)

DevTools listening on ws://[::1]:9222/devtools/browser/e729de03-88c4-4bc5-b12a-cecfe63ebf54
2018-06-13 14:47 : [info] MEO API started in development mode!
vagrant@vagrant:nodejs$ cat access-9.log
2018-06-13 14:37 : CHROME STDERR: [0613/143740.227105:ERROR:gpu_process_transport_factory.cc(1017)] Lost UI shared context.
2018-06-13 14:37 : CHROME STDERR: 
DevTools listening on ws://127.0.0.1:9222/devtools/browser/12f76570-7d3b-4426-8e42-6821ee7e440e
2018-06-13 14:37 : > It took 255ms to start and connect to Chrome (2 tries)
2018-06-13 14:37 : CHROME STDERR: [0613/143742.169722:ERROR:gles2_cmd_decoder.cc(3354)] ContextResult::kFatalFailure: fail_if_major_perf_caveat + swiftshader
2018-06-13 14:37 : CHROME STDERR: [0613/143742.172665:ERROR:gles2_cmd_decoder.cc(3354)] ContextResult::kFatalFailure: fail_if_major_perf_caveat + swiftshader
2018-06-13 14:37 : [info] MEO API started in development mode!
2018-06-13 14:40 : CHROME STDERR: [0613/144007.320494:ERROR:gpu_process_transport_factory.cc(1017)] Lost UI shared context.
2018-06-13 14:40 : CHROME STDERR: 
DevTools listening on ws://127.0.0.1:9222/devtools/browser/e2c7521b-85a0-4118-a5e8-d3bd607e8c0f
2018-06-13 14:40 : > It took 722ms to start and connect to Chrome (4 tries)
2018-06-13 14:40 : CHROME STDERR: [0613/144009.914110:ERROR:gles2_cmd_decoder.cc(3354)] ContextResult::kFatalFailure: fail_if_major_perf_caveat + swiftshader
2018-06-13 14:40 : CHROME STDERR: [0613/144009.916734:ERROR:gles2_cmd_decoder.cc(3354)] ContextResult::kFatalFailure: fail_if_major_perf_caveat + swiftshader
2018-06-13 14:40 : [info] MEO API started in development mode!
2018-06-13 14:40 : CHROME STDERR: [0613/144033.531034:ERROR:gpu_process_transport_factory.cc(1017)] Lost UI shared context.
2018-06-13 14:40 : CHROME STDERR: 
DevTools listening on ws://127.0.0.1:9222/devtools/browser/fe0b562e-ec43-49ee-b3e0-cc7565b42c7d
2018-06-13 14:40 : > It took 253ms to start and connect to Chrome (2 tries)
2018-06-13 14:40 : CHROME STDERR: [0613/144034.979060:ERROR:gles2_cmd_decoder.cc(3354)] ContextResult::kFatalFailure: fail_if_major_perf_caveat + swiftshader
2018-06-13 14:40 : CHROME STDERR: [0613/144034.981555:ERROR:gles2_cmd_decoder.cc(3354)] ContextResult::kFatalFailure: fail_if_major_perf_caveat + swiftshader
2018-06-13 14:40 : [info] MEO API started in development mode!
2018-06-13 14:44 : CHROME STDERR: [0613/144443.591714:ERROR:gpu_process_transport_factory.cc(1017)] Lost UI shared context.
2018-06-13 14:44 : CHROME STDERR: [0613/144443.597460:ERROR:socket_posix.cc(144)] bind() returned an error, errno=98: Address already in use (98)
2018-06-13 14:44 : CHROME STDERR: [0613/144443.597908:ERROR:socket_posix.cc(144)] bind() returned an error, errno=98: Address already in use (98)
2018-06-13 14:44 : CHROME STDERR: [0613/144443.598107:ERROR:devtools_http_handler.cc(292)] Cannot start http server for devtools. Stop devtools.
2018-06-13 14:44 : > It took 102ms to start and connect to Chrome (1 tries)
2018-06-13 14:44 : [info] MEO API started in development mode!
2018-06-13 14:45 : CHROME STDERR: [0613/144506.012671:ERROR:gpu_process_transport_factory.cc(1017)] Lost UI shared context.
2018-06-13 14:45 : CHROME STDERR: 
DevTools listening on ws://127.0.0.1:9222/devtools/browser/e7a898b0-4054-4d0f-baac-c4ab6bb012d3
2018-06-13 14:45 : > It took 253ms to start and connect to Chrome (2 tries)
2018-06-13 14:45 : CHROME STDERR: [0613/144507.913659:ERROR:gles2_cmd_decoder.cc(3354)] ContextResult::kFatalFailure: fail_if_major_perf_caveat + swiftshader
2018-06-13 14:45 : CHROME STDERR: [0613/144507.916606:ERROR:gles2_cmd_decoder.cc(3354)] ContextResult::kFatalFailure: fail_if_major_perf_caveat + swiftshader
2018-06-13 14:45 : [info] MEO API started in development mode!
2018-06-13 14:47 : > It took 102ms to start and connect to Chrome (1 tries)
2018-06-13 14:47 : CHROME STDERR: [0613/144724.027462:ERROR:gpu_process_transport_factory.cc(1017)] Lost UI shared context.
[0613/144724.034150:ERROR:socket_posix.cc(144)] bind() returned an error, errno=98: Address already in use (98)

Did this work before? N/A 

Chrome version: 67.0.3396.87  Channel: stable
OS Version: 16.04
Flash Version: 

const Nick = require("nickjs")
const nick = new Nick()

;(async () => {
	const tab = await nick.newTab()
	await tab.open("news.ycombinator.com")
	await tab.untilVisible("#hnmain") // Make sure we have loaded the page
	await tab.inject("../injectables/jquery-3.0.0.min.js") // We're going to use jQuery to scrape
	const hackerNewsLinks = await tab.evaluate((arg, callback) => {
		// Here we're in the page context. It's like being in your browser's inspector tool
		const data = []
		$(".athing").each((index, element) => {
			data.push({
				title: $(element).find(".storylink").text(),
				url: $(element).find(".storylink").attr("href")
			})
		})
		callback(null, data)
	})
	console.log(JSON.stringify(hackerNewsLinks, null, 2))
})()
.then(() => {
	console.log("Job done!")
	nick.exit()
})
.catch((err) => {
	console.log(`Something went wrong: ${err}`)
	nick.exit(1)
})

Comment 1 by masao.so...@gmail.com, Jun 14 2018 

I run the chrome in headless mode.

Comment 2 by krajshree@chromium.org, Jun 14 2018

Labels: Needs-Triage-M67

Comment 3 by alex...@chromium.org, Jun 14 2018

Components: Internals>Headless

Comment 4 by masao.so...@gmail.com, Jul 3 

Just wondering when are you going to fix it up?

Comment 5 by vamshi.kommuri@chromium.org, Jul 18

Cc: vamshi.kommuri@chromium.org
Labels: Triaged-ET Proj-Headless
Thanks for filing the issue!

As the issue seems to be related to Headless chrome hence adding appropriate label and requesting the respective team to have a look into this and help in further triaging it.

Comment 6 by susan.boorgula@chromium.org, Sep 4

Labels: TE-NeedsTriageHelp
Adding 'TE-NeedsTriageHelp' as per comment #5 and requesting Internals>Headless team to look into the issue and help in further triaging.

Thanks..
►

Sign in to add a comment