Extension Error: You must provide a url to the runner

[pjutard]

Lighthouse Version: 1.6.0
Chrome Version: 56.0.2924.87
URL: https://app.mural.ly/
Error Message: You must provide a url to the runner
Stack Trace:

   at Function.run (chrome-extension://blipmdconlkpinefehnmjammfjpmpbjk/scripts/lighthouse-background.js:13600:23)
   at window.runLighthouseForConnection (chrome-extension://blipmdconlkpinefehnmjammfjpmpbjk/scripts/lighthouse-background.js:14685:15)
   at connection.getCurrentTabURL.then.url (chrome-extension://blipmdconlkpinefehnmjammfjpmpbjk/scripts/lighthouse-background.js:14711:18)```

[ebidel]

Looks like #1214 may not have been fixed after all. As Paul mentioned, it's a hard one to repro and debug.

[awebdeveloper]

another duplicate bug #1819

[patrickhulce]

@centinel3 As a workaround are you able to successfully run against your site using the CLI?

[patrickhulce]

huge insight from @ev1stensberg in #2657 (comment)

FYI this happens if your initial URL fails and you try to rerun the extension straight away.

[patrickhulce]

more info from #2684

Always gets stuck on the HTTP Redirect test

[evenstensberg]

Could I fix this @patrickhulce ?

[patrickhulce]

@ev1stensberg yeah that'd be awesome thanks!

[brendankenny]

@ev1stensberg would you mind writing up a few notes on what you plan to do before you start?

It's not clear to me, at least, what the root cause is or how best to fix it :) e.g. #1834 (comment) from above seems helpful for tracking it down, but doesn't give a lot of insight on its own into what needs fixing

[evenstensberg]

Sure. I was planning to begin with this on monday, if that's fine? I've got an hypothesis now and that is that whenever the initial run fails ( first time you run the extension ) , the second time won't run properly, as it got stuck somewhere in the first instance. Doing a repro, which will give me more information. I get this pretty bug pretty often on my computer, so it's pretty easy to track down for me.

[evenstensberg]

Actually, lemme show you @brendankenny @patrickhulce :

https://www.youtube.com/watch?v=G3_EnydKi6A&feature=youtu.be

[evenstensberg]

Makes my hypothesis wrong, it's stuck on HTTP Redirect.

Edit: Possible that we do a comparison somewhere in Redirect that is dependent on initialURL, which is wrong or throws, because page automatically redirected. A note is that the extension runs properly if we do not run all categories. 3 or fewer is fine, but all throws the error.

[sambokai]

running into this issue as well..

[paulirish]

tracked by #5668 now.