Closed Bug 1601806 Opened 5 years ago Closed 5 years ago

Remove "Please close Firefox" prompt at end of installation

Categories

(Firefox :: Installer, enhancement, P1)

Unspecified
Windows
enhancement

Tracking

()

VERIFIED FIXED
Firefox 74
Tracking Status
firefox74 --- verified

People

(Reporter: molly, Assigned: molly)

Details

Attachments

(1 file)

Currently, if any Firefox instance is already running at the end of an installation when we would normally launch the new instance, we refuse to do so and show a message box instead. This is because you couldn't previously run two different installations if they would be trying to use the same profile (there are exceptions for dev edition, which always had its own profile). But now that we have per-install profiles, that eliminates the reason for the prompt, leaving it as just an annoyance that should be removed.

Taking this now as a fix for the issue reported in bug 1600905 comment 13.

Assignee: nobody → mhowell
Status: NEW → ASSIGNED
Type: defect → enhancement
Priority: P3 → P1

FYI, Romain, this change will cause us to no longer ever set the old_running column in the stub ping. The check for old instances couldn't detect any version released since March because of bug 1600905 and nobody noticed until last week when that was filed, so I'm guessing removing it isn't a problem.

At the end of any successful install, both the stub installer and full installer
(in interactive mode) attempt to launch the newly installed copy. But currently,
they first check if any copy of Firefox [1] is already running, and skip doing
that launch if so. The reason for this is that it used to be the case that no
two instances of Firefox could ever be running under default conditions because
there was only one default profile and it would be in use. It's clear that this
is the reason for the check because an exception is made for Developer Edition,
which had its own default profile and so wasn't subject to this restriction.

But now, we have per-install profiles by default, so there's no longer any need
to have this check, because launching the new instance won't be blocked by the
fact that there's already an instance running; all we're doing is creating
false positive prompts for something that isn't an issue anymore. So, this
patch removes the check and the prompt.

[1] At least that's the intent, but because of bug 1600905 we're actually now
checking for any Gecko-based product, because that's the best we can now do.

Great catch Molly.
It also helps now identified new window launch events that fail because of other reasons and we see that we get about 10k daily installs that succeed whilst failing to open Firefox upon install termination (these always show old_running as true). Should I open a new bug to investigate this? https://sql.telemetry.mozilla.org/queries/67052/source#169823

Well, the old_running check as it was does work to detect versions prior to 67. And there's nothing else that causes that particular flag to be set except for this one check (which this bug removes). So the only way I know of for that to be happening is for those pings to have really seen those older versions running (perhaps hanging in the background, but running somehow).

There's a r+ patch which didn't land and no activity in this bug for 2 weeks.
:mhowell, could you have a look please?
For more information, please visit auto_nag documentation.

Flags: needinfo?(mhowell)

I intentionally delayed landing this because it got its r+ on the last day before I left for two weeks, and I wasn't going to land anything that day. I'm back today so I'll do it now.

Flags: needinfo?(mhowell)
Pushed by mhowell@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/98bc6434d1ae Remove installer check for running instances before launching new instance. r=agashlin
Status: ASSIGNED → RESOLVED
Closed: 5 years ago
Resolution: --- → FIXED
Target Milestone: --- → Firefox 74

Confirming this issue as fixed using the installer of 74.0b4, build ID 20200216164042.
The "Please close Firefox" prompt at end of installation is no longer displayed.

Status: RESOLVED → VERIFIED
Flags: qe-verify+
QA Contact: cornel.ionce
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: