1531717 - The Telemetry status number for Windows Launcher Process does not update correctly

Status: RESOLVED INVALID

(Toolkit :: Telemetry, defect)

Description

[Rares Doghi, Desktop QA]

[Affected versions]:
Beta 67.0a1

[Affected platforms]:
Platforms: Windows

Steps :

1. Launch the Firefox Browser and reach about:support in order to check the Launcher Process status - Enabled
2. Reach about:telemetry#environment-data-tab_settings and search for Process.
3. Check the launcherProcessState = 0
4. Reach about config and toggle the browser.launcherProcess.enabled to FALSE.
5. Reach about:support in order to check the Launcher Process status - Disabled Forcibly
6. Reach about:telemetry#environment-data-tab_settings in a new tab and search for Process.

Expected Results :

The launcherProcessState = 2 should be displayed.

Actual Results :

The launcherProcessState = 0 status is displayed because it won't update.

Please note that if the user Opens the Firefox Browser and changes the browser.launcherProcess.enabled to FALSE before reaching about:telemetry the launcherProcessState status number is updated accordingly.

Comment 1

[Jan-Erik Rediger [:janerik]]

This value is determined by reading Services.appinfo.launcherProcessState once when building the environment for the first time.

I was under the impression that this value needs to be read once after startup and not change over the course of a session.

:aklotz provided the code (bug 1517639), can you confirm if the current behavior is correct?

Comment 2

[(No longer employed by Mozilla) Aaron Klotz]

We do not want telemetry to reflect the current state of the pref; we want telemetry to reflect what actually happened during startup.