-
-
Notifications
You must be signed in to change notification settings - Fork 33.3k
Closed
Labels
questionIssues that look for answers.Issues that look for answers.wrong repoIssues that should be opened in another repository.Issues that should be opened in another repository.
Description
- Node v6
- Darwin
I am getting a null exit code after launching and killing a child process. This probably should never happen? It's happening when I launch chrome in headless mode:
When using the 'chrome-launcher' module, everything works normally:
const cl = require('chrome-launcher');
cl.launch({
startingUrl: `http://localhost:${port}/suman_testing?data=${testData}`,
chromeFlags: []
})
.then(c => {
// c.launcher.chrome is a child process instance
c.launcher.chrome.once('exit', function(code){
// exit code is an integer
});
});
but when I use headless mode:
const cl = require('chrome-launcher');
cl.launch({
startingUrl: `http://localhost:${port}/suman_testing?data=${testData}`,
chromeFlags: ['--headless'] // <<< use headless mode <<<
})
.then(c => {
c.launcher.chrome.once('exit', function(code){
// exit code is null !! <<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<
});
});
is this expected? I am assuming this should never happen.
Metadata
Metadata
Assignees
Labels
questionIssues that look for answers.Issues that look for answers.wrong repoIssues that should be opened in another repository.Issues that should be opened in another repository.