Lighthouse: three.js different results and error

[sanprieto]

Feature request summary

Hello I have created a new project with three.js and bootstrap. I check with audit and insights and I have a very different results.
Are the special features of this library (three.js) being taken into account while doing the analysis?
Sometimes shows this error:

Lighthouse returned error: INTERNAL: Extension result empty. Lighthouse calling Page.navigate with https://sanprieto.es/newProject/ Uncaught (in promise) Error: Extension timed out. No call to exit() before render timeout. at wrs.Extension.onTimeout_ (http://ghost-rider/devtools_script_api.js:5567:13) at http://ghost-rider/devtools_script_api.js:669:9 at Map.forEach (<anonymous>) at chromium.DevTools.Connection.dispatchMessage (http://ghost-rider/devtools_script_api.js:668:76) at chromium.DevTools.Connection.onJsonMessage_ (http://ghost-rider/devtools_script_api.js:650:65) at <anonymous>:1:40

Are you willing to work on this yourself?
I'm not sure if i have enough level but yes I am.

What is the motivation or use case for changing this?
Because currently there are a lot of project create with three.js

How is this beneficial to Lighthouse?
Because with a good analysis is possible to improve the project.

Run LH on https://sanprieto.es/newProject/

versions
chrome 80.0.3987.100
├── stats.[email protected]
├── [email protected]
└── [email protected]
bootstrap 4.4

[patrickhulce]

I couldn't reproduce that exact behavior but that page definitely has abnormal behavior on PSI. We'll look into it.

[connorjclark]

LR infra must do webgl in software, that is why it's so slow :(

one option would be to disable webgl in WRS - canvas might be faster? this is assuming most pages support canvas fallback

[connorjclark]

We could possibly detect heavy webgl usage and emit a warning in PSI.