"Lighthouse is warming up..."

[Th3S4mur41]

and never goes beyond the following screen in Edge Canary

It is working fine in the stable Edge on the same machine though.

Probably related to the same issue in Chrome

AB#45665567

[captainbrosset]

Thank you for reporting this. I was able to reproduce this locally on Edge Canary 117 on Windows 11.
I will make sure this shows up on our team's backlog for investigation/prioritization/fixing.

[yksht]

I have same issue.

Microsoft Edge
Version 115.0.1901.183 (Official build) (64-bit)

Windows 11 Pro 22H2
OS Build 22621.1992

[spanishgringo]

Same issue Version 115.0.1901.188 (Official build) (arm64)
MacOs Ventura 13.5 with M2

I've tried workarounds from the the threads about this bug in Chrome but none have worked:
chrome://restart
enabling "legacy navigation"
etc.

[Randomblock1]

Same issue
Edge 115.0.1901.188 (Official build) (64-bit)
Windows 11 Pro 22H2
OS build 22621.2070

[J6ey]

Frustrated.
Version 115.0.1901.188 (Official build) (64-bit)

[mustafa-barakat]

Version 115.0.1901.188 (Official build) (64-bit)
Version 117.0.2024.0 (Official build) canary (64-bit)

Both aren't working with any website; chrome is performing these tests on the same websites fine.

[PIndividual]

Same here
Version 115.0.1901.200 (Official build) (64-bit)
Windows 10 Pro for Workstations 22H2

[Ashbri4]

What about a link for android 14 Get Outlook for Android<https://aka.ms/AAb9ysg>

…

________________________________ From: GASP3D4L ***@***.***> Sent: Tuesday, August 8, 2023 4:21:06 AM To: MicrosoftEdge/DevTools ***@***.***> Cc: Subscribed ***@***.***> Subject: Re: [MicrosoftEdge/DevTools] "Lighthouse is warming up..." (Issue #169) Same here Version 115.0.1901.200 (Official build) (64-bit) Windows 10 Pro for Workstations 22H2 — Reply to this email directly, view it on GitHub<#169 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/A2ZI6OFZCINWT3WTW6446QDXUHZHFANCNFSM6AAAAAA2UXNGGQ>. You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>

[betorina]

This problem is unfortunately still happening...
it's not working in either 114 and 115 (tried all possible tips/fixes, and also an Edge Beta & Canary version)
NB Chrome + Lighthouse is working fine on same machine.

Version 115.0.1901.200 (Official build) (arm64)
Mac M2 Pro - Ventura 13.5

[indexxing]

Same here on Edge Dev (Windows 11)

[jamierytlewski]

Same.

[glimpsedchaos]

Same issue - Edge Version 115.0.1901.183

[Th3S4mur41]

It's working again for me in Edge 117.0.2039.0 (Official build) canary (64-bit) on Windows 11
Still broken on the same system on stable Edge (115.0.1901.203)

[ankityadav4]

This problem is still happening.

[mabdelfattah]

Not working - Version 116.0.1938.54 (Official build) Beta (arm64) - MacOS

[captainbrosset]

Thanks for your patience. Our engineering team is still investigating this. A preliminary fix went into 117 already.

[betorina]

A preliminary fix went into 117 already.

Please test... before giving 'good' news.
Still no luck – lighthouse still hangs – on Version 117.0.2045.1 (Mac M2)

Update: It is solved in 117 (Wonderful!)

[captainbrosset]

Thanks for the additional reports and error stack trace. This is still on our backlog and being actively investigated.

[dviate]

Here's my addition, I'm having the same issues on both *.local and remote servers. Some info from edge://version below.

It happens in my regular browser (data below), but also in the latest Canary version (117.0.2044.0 (Official build) Canary (arm64)) without any active extensions.

Microsoft Edge
116.0.1938.54 (Official build) (arm64)

Revision
e584466f74bf872ad84fcd188ddc4b60fd2ec646

Chromium version
116.0.5845.97

Operating system
macOS Version 13.5.1 (Build 22G90)

JavaScript
V8 11.6.10.8

User agent
Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/116.0.0.0 Safari/537.36 Edg/116.0.1938.54

Command-line
/Applications/Microsoft Edge.app/Contents/MacOS/Microsoft Edge --flag-switches-begin --enable-experimental-web-platform-features --enable-features=msBackspaceKeyNavigatePageBack --flag-switches-end

[captainbrosset]

Some updates from our end after researching this a bit more:

There are 2 issues at play here, manifesting in a similar way:

1. Lighthouse stays stuck with the message "Lighthouse is warming up..."
2. Lighthouse stays stuck with an exception displayed in the popup "Exception: could not create page handle for target tab".

Issue 1 happens in 116 (which is the current stable version of Edge). I announced earlier that we had made a fix in 117. The plan was to cherry pick this fix to 116 too, but that unfortunately did not happen. The fix was correct for issue 1, but then issue 2 occured, which is why you all still had a broken Lighthouse.

Issue 2 happens in 117 and 118. We have a fix for this that's ready to roll out, and should be going to 118 (Canary and Dev) any time now. It will also make it to 117 (Beta) probably next week.

You can enable this fix today yourself:

1. Open the edge://flags page.
2. In the search field, at the top, enter "DevTools using Tab Target".
3. Change the flag's value from "Default" to "Enabled".
4. Restart the browser.

Lighthouse should now work.
Note that this flag will be enabled by default in Edge very soon. So this is only if you want to use Lighthouse right now in Beta, Dev, or Canary.

So, bottom line is: it unfortunately looks like lighthouse is broken in stable and we won't be able to repair it there. But there's a fix you can do to get it to run in Beta, Dev, Canary. And that fix will be applied for you very soon (probably via the Edge updater in the September timeframe).

Note that Stable will soon become 117 (it's planned for 2023-09-14).

[Th3S4mur41]

Confirmed here too working in Edge Canary 118.0.2071.0 with edge://flags/#devtools-tab-target enabled

[robearlam]

Confirmed here as well.

Working in Edge 118.0.2060.1 with edge://flags/#devtools-tab-target enabled

[AngeloKarugo]

This has been resolved for me after updating to 116.0.1938.81 on stable build, without enabling any flags.
OS info:
Windows 10 Pro (build 19045.3393)

[J6ey]

@AngeloKarugo Can confirm 116.0.1938.81 (Official build) (64-bit) is working on Windows 11 Home

[mpotane]

Working for me as well thanks same build 116.0.1938.81

[captainbrosset]

Awesome, thank you for confirming. Closing this issue now.