[BUG] Lighthouse performance is returning NULL most of the time

Environment

• chrome-aws-lambda Version: 7.0.0
• puppeteer / puppeteer-core Version: 7.1.0
• OS: Mac
• Node.js Version: 12.x
• Lambda / GCF Runtime: nodejs12.x

Expected Behavior

Google Lighthouse executed successfully and always returns Performance score

Current Behavior

Google Lighthouse executed successfully BUT most of the time Performance score is null.

Steps to Reproduce

I created a github repo to help reproduce the error.

https://github.com/wafendy/aws-lambda-lighthouse-docker

main branch: Using the latest version which is v7.0.0 last-known-working branch: Using version v3.1.1

v3.1.1 is last known stable version for my setup.

Possible Solution

chrome-aws-lambda v3.1.1 is the last known working version, but it has may security vulnerabilities and no more updates to addresss the vulnerabilities.

Perhaps, I’m using it wrongly or there is missing configuration.

[ACAHNN]

In case this is helpful for anyone. I was having this issue when driving lighthouse via puppeteer. What fixed it for me was removing an argument that is passed to chromium. Specifically, I was using the --single-process flag. Commenting this out did the trick for me.

[code]

await puppeteer.launch({
	    ignoreHTTPSErrors: true,
	    headless: true,
	    args: [//'--single-process',
		   '--no-zygote',
		   '--no-sandbox',
		  ]
	});

[configuration]

node: 14.16.0 lighthouse: 7.2.0 puppeteer: 8.0.0 platform(s): macOS Big Sur (local), Ubuntu 20.04 (remote EC2 instance)

[louist7]

We found that increasing the memory on the lambda function to 2048 MB, and the timeout to 300 seconds, improved the reliability of the results enough for us to be able to use it.