Invalid_url when trying to run in Incognito

[tsgoldladder]

FAQ

• Yes, my issue is not about variability or throttling.
• Yes, my issue is not about a specific accessibility audit (file with axe-core instead).

URL

https://measurable.energy

What happened?

INVALID_URL

Channel: DevTools
Initial URL: 
Chrome Version: 122.0.0.0
Stack Trace: LighthouseError: INVALID_URL
    at UrlUtils.normalizeUrl (devtools://devtools/bundled/devtools-frontend/front_end/third_party/lighthouse/lighthouse-dt-bundle.js:253:109917)
    at devtools://devtools/bundled/devtools-frontend/front_end/third_party/lighthouse/lighthouse-dt-bundle.js:457:12406
    at Runner.gather (devtools://devtools/bundled/devtools-frontend/front_end/third_party/lighthouse/lighthouse-dt-bundle.js:450:3581)
    at navigationGather (devtools://devtools/bundled/devtools-frontend/front_end/third_party/lighthouse/lighthouse-dt-bundle.js:457:12377)
    at async navigation (devtools://devtools/bundled/devtools-frontend/front_end/third_party/lighthouse/lighthouse-dt-bundle.js:457:13727)
    at async a (devtools://devtools/bundled/devtools-frontend/front_end/entrypoints/lighthouse_worker/lighthouse_worker.js?remoteBase=https%3A%2F%2Fchrome-devtools-frontend.appspot.com%2Fserve_file%2F%409d4c1072da62b411b351a38b9ed6214ab236aa7b%2F:1:2166)
    at async self.onmessage (devtools://devtools/bundled/devtools-frontend/front_end/entrypoints/lighthouse_worker/lighthouse_worker.js?remoteBase=https%3A%2F%2Fchrome-devtools-frontend.appspot.com%2Fserve_file%2F%409d4c1072da62b411b351a38b9ed6214ab236aa7b%2F:1:2527)

What did you expect?

Normal lighthouse report function. Wouldn't begin.

What have you tried?

Mobile and Desktop scans.
Mode: Nav
Categories: Performance, Accessibility

How were you running Lighthouse?

Chrome DevTools

Lighthouse Version

not sure

Chrome Version

122.0.6261.111

Node Version

No response

OS

Windows 10

Relevant log output

Channel: DevTools
Initial URL: 
Chrome Version: 122.0.0.0
Stack Trace: LighthouseError: INVALID_URL
    at UrlUtils.normalizeUrl (devtools://devtools/bundled/devtools-frontend/front_end/third_party/lighthouse/lighthouse-dt-bundle.js:253:109917)
    at devtools://devtools/bundled/devtools-frontend/front_end/third_party/lighthouse/lighthouse-dt-bundle.js:457:12406
    at Runner.gather (devtools://devtools/bundled/devtools-frontend/front_end/third_party/lighthouse/lighthouse-dt-bundle.js:450:3581)
    at navigationGather (devtools://devtools/bundled/devtools-frontend/front_end/third_party/lighthouse/lighthouse-dt-bundle.js:457:12377)
    at async navigation (devtools://devtools/bundled/devtools-frontend/front_end/third_party/lighthouse/lighthouse-dt-bundle.js:457:13727)
    at async a (devtools://devtools/bundled/devtools-frontend/front_end/entrypoints/lighthouse_worker/lighthouse_worker.js?remoteBase=https%3A%2F%2Fchrome-devtools-frontend.appspot.com%2Fserve_file%2F%409d4c1072da62b411b351a38b9ed6214ab236aa7b%2F:1:2166)
    at async self.onmessage (devtools://devtools/bundled/devtools-frontend/front_end/entrypoints/lighthouse_worker/lighthouse_worker.js?remoteBase=https%3A%2F%2Fchrome-devtools-frontend.appspot.com%2Fserve_file%2F%409d4c1072da62b411b351a38b9ed6214ab236aa7b%2F:1:2527)

[adamraine]

I can't reproduce this, but we did fix a cause of the INVALID_URL error in M123 and looks like you are on M122.

Does this work using a newer version of Chrome (e.g. Chrome beta)?

[tsgoldladder]

Ah ok, maybe my Chrome was not updated at the time. I mainly reported on this to help the project, since the error logs asked me to if the error persisted which it did - but it looks like you've solved it already!

…

On Wed, 6 Mar 2024 at 18:44, Adam Raine ***@***.***> wrote: I can't reproduce this, but we did fix a cause <https://issues.chromium.org/issues/41490473> of the INVALID_URL error in M123 and looks like you are on M122. Does this work using a newer version of Chrome (e.g. Chrome beta)? — Reply to this email directly, view it on GitHub <#15855 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AJFPCEJ5JXBKYNPSHX2UG2DYW5PX7AVCNFSM6AAAAABEIZ734GVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSOBRGU2TIMBZHA> . You are receiving this because you authored the thread.Message ID: ***@***.***>