error on scanning damettoluca.com

Provide the steps to reproduce

1. Run LH on damettoluca.com
2. Run LH on user.damettoluca.com

What is the current behavior?

Lighthouse returned error: INTERNAL: Extension result empty. Lighthouse calling Page.navigate with http://damettoluca.com/ 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:5555:13) at http://ghost-rider/devtools_script_api.js:708:9 at Map.forEach (<anonymous>) at chromium.DevTools.Connection.dispatchMessage (http://ghost-rider/devtools_script_api.js:707:76) at chromium.DevTools.Connection.onJsonMessage_ (http://ghost-rider/devtools_script_api.js:689:65) at <anonymous>:1:40 

PROTOCOL_TIMEOUT

Channel: DevTools
Initial URL: https://damettoluca.com/
Chrome Version: 79.0.3945.88
Stack Trace: LHError: PROTOCOL_TIMEOUT
    at eval (devtools://devtools/remote/serve_file/@c2a58a36b9411c80829b4b154bfcab97e581f1f3/audits_worker/audits_worker_module.js:1268:229)

for damettoluca.com and a normal result for user.damettoluca.com

What is the expected behavior?

LH should return my website infos and stats in damettoluca.com and user.damettoluca.com

Environment Information

• Affected Channels: All, also the one from google pagespeed insights
• Lighthouse version: latest (?)
• Chrome version: 79.0.3945.88 (official build) (64 bit)
• Node.js version: 12.14.0
• Operating System: windows 10 1909 64bit

[patrickhulce]

Are you saying that if I put a debugger in the console mid run it shouldn’t stop a run, because it seems to for me?

I’m saying if the page has a regular debugger statement in the middle of a run, Lighthouse should not pause for it. If a user action in console injects a debugger statement, that’s probably a different story (it’d be smart of DevTools to re-enable pauses if the user adds a debugger statement like that for example, so maybe that’s happening?)

Now it sounds like @LucaTheHacker’s approach is specifically to spam and lock up DevTools whenever it’s inspected, so I’d think all bets are off there.

Idk why it cannot load without executing in the normal way the js code and check just the website functionality.

Because in order to tell you debug information about the page like Lighthouse does, we need to debug the page! 😉

[connorjclark]

Lighthouse requires Devtools debugging to work on a page. Don’t attack debuggers and Lighthouse will work for you.