1777969 - Microsoft Store edition starts very slowly

Status: NEW

(Firefox :: Installer, defect, P5)

Description

[Fei Yang [:fei1yang]]

Attachment: Errors gathered from "Browser Console"

User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:102.0) Gecko/20100101 Firefox/102.0

Steps to reproduce:

1. Install Firefox 102.0.0.0 via Microsoft Store on Windows 11 Enterprise 21H2 22000.739
2. Open Firefox

(There is no field for other software versions so I put them here.)

Actual results:

The Firefox installation stuck in loading stage where the window is completely white or all dynamic elements are placeholders for about 10 seconds when being opened

Expected results:

The Firefox installation can be controlled by the user almost immediately when being opened

Comment 1

[[e-mail] (:bhearsum)]

Based on seeing some non-virtualized paths in your log (thank you for that!), this may ultimately be the same issue as https://bugzilla.mozilla.org/show_bug.cgi?id=1730498, although it's tough to be sure. It certainly sounds like there's a bit of weirdness going on in the profile handling code.

A few questions:

• Do you have any non-Store installations of Firefox? Are they running when you try to open the Store version?
• Does startup always take this long, or is it only slow the first time after installation?
• Do you have any files or directories in %LocalAppData%\Packages\Mozilla.Firefox_n80bbvh6b1yt2\LocalCache\Roaming\Mozilla\Firefox\Profiles.
• How many profiles do you have in C:\Users\[REDACTED]\AppData\Roaming\Mozilla\Firefox\Profiles?
• Do you have any of the same profile directories in two directories above?

Comment 2

[Fei Yang [:fei1yang]]

• No when this issue appears, however I did installed it in an attempt to find out whether this issue also affects non-Store installations and deleted it and all related directories afterwards
• It always take this long
• Yes
• This directory does not exist
• No due to the reason above

Comment 3

[[e-mail] (:bhearsum)]

(In reply to Fei Yang [:fei1yang] from comment #2)

• No when this issue appears, however I did installed it in an attempt to find out whether this issue also affects non-Store installations and deleted it and all related directories afterwards
• It always take this long
• Yes
• This directory does not exist
• No due to the reason above

Thank you, this helps a little bit. A couple follow-ups:

• Does C:\Users\[REDACTED]\AppData\Roaming\Mozilla\ exist at all? If so, what are the contents?
• Can you attach the contents of about:support?

It's very curious that Firefox appears to be looking in a non-virtualized location for things like search.json, particularly when you have no other Firefox installations.

Comment 4

[Fei Yang [:fei1yang]]

Attachment: Content of "about:support"

• This directory also does not exist
• Contents of about:support are attached

Comment 5

[[e-mail] (:bhearsum)]

(In reply to Fei Yang [:fei1yang] from comment #4)

Created attachment 9284365 [details]
Content of "about:support"

• This directory also does not exist
• Contents of about:support are attached

Thank you again. I want to be really, really certain about one thing: is the [REDACTED] part of your reports simply your username, or is it something more like $username\Packages\Mozilla.Firefox_n80bbvh6b1yt2? Everything you've attached suggests that Firefox thinks the profile is in a directory like c:\users\$username\AppData\Roaming\Mozilla\Firefox\Profiles -- but that directory doesn't seem to exist.

What happens when you click the "Open Folder" button for the profile in about:support? Does explorer open correctly? If so, to which folder?

Comment 6

[Fei Yang [:fei1yang]]

• [REDACTED] in C:\Users[REDACTED]\ is my username and [REDACTED] in Mozilla\Firefox\Profiles\moi78xyh.[REDACTED]\ is the profile name.
• It try to open the non-virtualized path and explorer fail to open it with "Location is not available" error

Comment 7

[[e-mail] (:bhearsum)]

Alright, I'm pretty convinced this is rooted in the same issues as bug 1730498, which we have no good solution for at the moment :(. The best I can offer is to use the regular Firefox installer for now. We're hoping to make a change towards the end of this year that is likely to fix this issue.