Closed sattaman closed 6 years ago
Hi @sattaman,
Is Chrome installed on you machine?
Here is the search logic:
export function win32() {
const installations: Array<string> = [];
const suffixes = [
'\\Google\\Chrome SxS\\Application\\chrome.exe', '\\Google\\Chrome\\Application\\chrome.exe'
];
const prefixes =
[process.env.LOCALAPPDATA, process.env.PROGRAMFILES, process.env['PROGRAMFILES(X86)']];
const customChromePath = resolveChromePath();
if (customChromePath) {
installations.push(customChromePath);
}
prefixes.forEach(prefix => suffixes.forEach(suffix => {
const chromePath = path.join(prefix, suffix);
if (canAccess(chromePath)) {
installations.push(chromePath);
}
}));
return installations;
}
from https://github.com/GoogleChrome/lighthouse/blob/master/chrome-launcher/chrome-finder.ts
@dotneet This was working previously, is working again on a restart. It has happened on a couple of machines though so maybe something else going on? I'll close now anyhow
@sattaman I'm late but maybe someone else lands here: This happens if a test breaks (exception, timeout or similar). The started chrome processes are not always killed. I have this problem regularly.
Infact i'm running pkill -f "(chrome)*?(--headless)"
to get rid of stale chrome instances in a cleanup script after chromy should be done.
I'm not sure with repo this issue belongs in.