Closed Bug 1517636 Opened 11 months ago Closed 11 months ago

Add launcher process state to about:support

Categories

(Toolkit :: Startup and Profile System, enhancement)

Unspecified
Windows
enhancement
Not set

Tracking

()

RESOLVED FIXED
mozilla66
Tracking Status
firefox66 --- fixed

People

(Reporter: aklotz, Assigned: aklotz)

References

Details

Attachments

(2 files)

Once we have pref reflection we can do this.
Blocks: 1517639
Pushed by aklotz@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/447687e20dac
Add launcher process state to about:support; r=Felipe,flod
Pushed by dluca@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/1f0d9b94c057
Follow-up - fix eslint error; r=bustage
Status: ASSIGNED → RESOLVED
Closed: 11 months ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla66

'browser.launcherProcess.enabled' - true I get this:
Launcher Process Disabled due to failure

'browser.launcherProcess.enabled' - false
Launcher Process Disabled forcibly

Is this normal?

(In reply to Gary [:streetwolf] from comment #6)

'browser.launcherProcess.enabled' - true I get this:
Launcher Process Disabled due to failure

'browser.launcherProcess.enabled' - false
Launcher Process Disabled forcibly

Is this normal?

It is normal in the sense that such a result is plausible, though something must have gone wrong to indicate a failure. Ideally we want most users to have enabled launcher processes.

Is there a remedy for this?

(In reply to Gary [:streetwolf] from comment #8)

Is there a remedy for this?

The first step would be for you to let me know what the values are under this registry key:
HKEY_CURRENT_USER\Software\Mozilla\Firefox\Launcher

Flags: needinfo?(garyshap)

Windows Registry Editor Version 5.00

[HKEY_CURRENT_USER\Software\Mozilla\Firefox\Launcher]
"C:\Program Files\Nightly\firefox.exe|Image"=dword:5c3f18a8
"C:\Program Files\Nightly\firefox.exe|Browser"=hex(b):00,00,00,00,00,00,00,
00

Flags: needinfo?(garyshap)

That state is indicative of 'browser.launcherProcess.enabled' = false

Please set the pref back to true, restart your browser, and then provide the values again.

Flags: needinfo?(garyshap)

I changed it to true and now about:support says Launcher Process Enabled.

Windows Registry Editor Version 5.00

[HKEY_CURRENT_USER\Software\Mozilla\Firefox\Launcher]
"C:\Program Files\Nightly\firefox.exe|Image"=dword:5c3f18a8
"C:\Program Files\Nightly\firefox.exe|Launcher"=hex(b):7d,fc,c6,2b,0b,00,00,
00
"C:\Program Files\Nightly\firefox.exe|Browser"=hex(b):a4,b7,c7,2b,0b,00,00,
00

Flags: needinfo?(garyshap)

Okay, great. If you ever see "Disabled due to failure" again, please ping me with the values of that registry key and I can give you more information.

Another failure.
Launcher Process Disabled due to failure

[HKEY_CURRENT_USER\Software\Mozilla\Firefox\Launcher]
"C:\Program Files\Nightly\firefox.exe|Image"=dword:5c3f18a8
"C:\Program Files\Nightly\firefox.exe|Launcher"=hex(b):72,bd,69,f4,01,00,00,
00
"C:\Program Files\Nightly\firefox.exe|Browser"=hex(b):00,00,00,00,00,00,00,
00

I set the pref to false, restarted Fx and it said Disabled forcibly. I then set the pref to true, restarted Fx and once again it's enabled. Does this tell you anything about my problem?

Aaron.

I've discovered that if I change my CPU speed in my BIOS and then boot up Windows and start Fx I get the about:support message that the Launcher Process failed. Why would changing the clock speed of my CPU cause this?

You need to log in before you can comment on or make changes to this bug.