1778082 - about:profiles no longer shows the currently running profile

Status: VERIFIED FIXED

(Toolkit :: Startup and Profile System, defect)

Description

[Dave Townsend [:mossop]]

In current nightlies on at least macOS and linux going to about:profiles does not show which profile is in use. Additionally nsIToolkitProfileService::currentProfile is null indicating that this is some internal failure. This problem does not occur on beta.

Comment 1

[Dave Townsend [:mossop]]

This problem appears to have been caused by https://hg.mozilla.org/integration/autoland/rev/f79083f74800.

The change has broken the way we ensure there is only one instance of the profile service in the process. The old XPCOM factory that was defined used to check whether a singleton instance had already been created and if so return that. The very first instance however is not created via XPCOM.

So on startup we now create the instance that we use to determine the current profile but anything later that attempts to get the profile service via XPCOM ends up getting a second instance that knows nothing about how the application was launched.

Comment 2

[Dave Townsend [:mossop]]

Attachment: Bug 1778082: Ensure nsToolkitProfileService is a singleton regardless of how it is accessed. r=kmag

Comment 3

[BugBot [:suhaib / :marco/ :calixte]]

Set release status flags based on info from the regressing bug 1773770

Comment 4

[Pulsebot]

Pushed by [e-mail]:
https://hg.mozilla.org/integration/autoland/rev/21abd775681d
Ensure nsToolkitProfileService is a singleton regardless of how it is accessed. r=kmag

Comment 5

[Norisz Fay [:noriszfay]]

https://hg.mozilla.org/mozilla-central/rev/21abd775681d

Comment 6

[Ardelean Oana, Desktop Test Engineering [:oardelean]]

Hello,
I managed to reproduce this issue on Nightly 104.0a1(build ID: 20220705212856) on Ubuntu 22.04. Verified as fixed on Firefox 104.0(build ID: 20220816115024) and Nightly 105.0a1(build ID: 20220816190318) on Ubuntu 22.04, macOS 12 and Windows 10.