After upgrade to Firefox 67.0 x64 Firefox crashes at startup with error code 0xc0000005
Categories
(Firefox :: General, defect, P1)
Tracking
()
People
(Reporter: mpfister, Assigned: toshi)
Details
(Keywords: crash)
Attachments
(1 file)
|
15.12 KB,
image/jpeg
|
Details |
FF67_crash.jpg
User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:67.0) Gecko/20100101 Firefox/67.0
Steps to reproduce:
Customized FF 66.0.5 x64 installed on Windows 10 1803 x64 clients.
Upgrade to Firefox 67.0 x64 via Microsft SCCM.
Actual results:
Firefox 67.0 crashes immediately with hex code 0xc0000005 (see attached screenshot)
After starting Firefox.exe once as an administrator the problem seems to be gone
Expected results:
Firefox starts
start firefox.exe -safe-mode -> same crash
enabled toolkit.crashreporter.enabled true in my mozilla.cfg -> same crash, no report in %APPDATA%\Roaming, \Mozilla folder not present
-> %programdata\Mozilla\ exists, but no crash report
Tried to create a strack trace, hth:
0:000> k
Child-SP RetAddr Call Site
00 000000a4b11ff628 00007ffd8c577e53 ntdll!NtTerminateProcess+0x14
01 000000a4b11ff630 00007ffd8b86ca7a ntdll!RtlExitUserProcess+0xe3
02 000000a4b11ff730 00007ffd8902cc08 KERNEL32!ExitProcessImplementation+0xa
03 000000a4b11ff760 00007ffd8902cbbb ucrtbase!exit_or_terminate_process+0x40
04 000000a4b11ff790 00007ff63a0a6f6f ucrtbase!common_exit+0x6f
05 000000a4b11ff7e0 00007ffd8b864034 firefox!__scrt_common_main_seh+0x173 [f:\dd\vctools\crt\vcstartup\src\startup\exe_common.inl @ 295]
06 000000a4b11ff820 00007ffd8c5a3691 KERNEL32!BaseThreadInitThunk+0x14
07 000000a4b11ff850 0000000000000000 ntdll!RtlUserThreadStart+0x21
If I install FF67 by manually calling the installation script (we are using it for ages) from an administrative user command prompt, FF works fine.
If I then uninstall FF and open a command prompt as the SYSTEM user (via PSEXEC -i -s -d CMD) and call the same installation batch, Firefox crashes at startup.
Since we're deploying FF unsing SCCM all installations running under SYSTEM.
This was never a problem until now. Tested the same procedure with FF 66.0.5, no crash
"After starting Firefox.exe once as an administrator the problem seems to be gone"
Only true if the user himself is an administrator on the system and can start Firefox.exe via an UAC prompt.
Other users on the same system are still affected.
|
||
Updated•5 years ago
|
Just tested with FF 67.0.1 x64 - same error message/problem
Just tested with FF 67.0.2 x64 - same error message/problem
Did some more debugging with FF 67.0.2 x64 German, still hoping someone will take care of this thread ;-)
firefox!mozilla::LauncherMain+0x515:
00007ff617dc45d5 80bc24d000000000 cmp byte ptr [rsp+0D0h],0 ss:000000ca9e3ff9f0=00
0:000> p
firefox!mozilla::LauncherMain+0x51d:
00007ff617dc45dd 0f84e7000000 je firefox!mozilla::LauncherMain+0x60a (00007ff617dc46ca) [br=1]
0:000> p
firefox!mozilla::LauncherMain+0x60a:
00007ff617dc46ca 4889d9 mov rcx,rbx 0:000> p firefox!mozilla::LauncherMain+0x60d: 00007ff617dc46cd ff159db80400 call qword ptr [firefox!_imp_ResumeThread (00007ff617e0ff70)] ds:00007ff617e0ff70={KERNEL32!ResumeThreadStub (00007ffb34e3cb10)} 0:000> t KERNEL32!ResumeThreadStub: 00007ffb34e3cb10 48ff25a9a90500 jmp qword ptr [KERNEL32!_imp_ResumeThread (00007ffb34e974c0)] ds:00007ffb34e974c0={KERNELBASE!ResumeThread (00007ffb3221a1b0)} 0:000> t KERNELBASE!ResumeThread: 00007ffb3221a1b0 4883ec28 sub rsp,28h
0:000> t
KERNELBASE!ResumeThread+0x4:
00007ffb3221a1b4 488d542438 lea rdx,[rsp+38h] 0:000> t KERNELBASE!ResumeThread+0x9: 00007ffb3221a1b9 ff15218f1100 call qword ptr [KERNELBASE!_imp_NtResumeThread (00007ffb323330e0)] ds:00007ffb323330e0={ntdll!NtResumeThread (00007ffb3586b3d0)} 0:000> t ntdll!NtResumeThread: 00007ffb3586b3d0 4c8bd1 mov r10,rcx
0:000> t
ntdll!NtResumeThread+0x3:
00007ffb3586b3d3 b852000000 mov eax,52h 0:000> t ntdll!NtResumeThread+0x8: 00007ffb3586b3d8 f604250803fe7f01 test byte ptr [SharedUserData+0x308 (000000007ffe0308)],1 ds:000000007ffe0308=00
0:000> t
ntdll!NtResumeThread+0x10:
00007ffb3586b3e0 7503 jne ntdll!NtResumeThread+0x15 (00007ffb3586b3e5) [br=0]
0:000> t
ntdll!NtResumeThread+0x12:
00007ffb3586b3e2 0f05 syscall 0:000> t ntdll!NtResumeThread+0x14: 00007ffb3586b3e4 c3 ret
Finally. Since there is no reply to this thread I finally found a kind workaround (tested with FF 67.0.4 x64 German on Windows 10 1803 x64).
During the start of Firefox, after being installed via SCCM/ (LOCAL SYSTEM) 3!!! registry entries will be created under HKEY_CURRENT_USER
[HKEY_CURRENT_USER\Software\Mozilla\Firefox\Launcher]
"C:\Program Files\Mozilla Firefox\firefox.exe|Image"=dword:5d0adee5
"C:\Program Files\Mozilla Firefox\firefox.exe|Launcher"=hex(b):43,4d,92,05,
03,00,00,00
"C:\Program Files\Mozilla Firefox\firefox.exe|Browser"=hex(b):12,a2,93,05,
03,00,00,00
Now FF crashes. As long as the registry entries exist, Firefox always crahes at startup.
You could either remove just the ...|Launcher entry or recreate it as REG_DWORD. Both actions would help.
I have no idea what the qword/dword values mean. But after setting them to 0 Firefox still starts normally so the actual value seems to be not so important.
Probably have to do this per Group Policy Preferences
"Your mileage may vary"
:-)
PS: While installing Firefox as admin user (not LOCAL SYSTEM) just the key/value
[HKEY_CURRENT_USER\Software\Mozilla\Firefox\Launcher]
"C:\Program Files\Mozilla Firefox\firefox.exe|Browser"=hex(b):0
is created. Now FF starts as well!
Still any other user starting it it will crash again
<?xml version="1.0"?>
<RegistrySettings clsid="{A3CCFC41-DFDB-43a5-8D26-0FE8B954DA51}"><Registry clsid="{9CD4B2F4-923D-47f5-A062-E897DD1DAD50}" name="C:\Program Files\Mozilla Firefox\firefox.exe|Launcher" status="C:\Program Files\Mozilla Firefox\firefox.exe|Launcher" image="13" changed="2019-06-26 10:45:46" uid="{7999D600-998E-461C-8E43-CF05053232F2}" bypassErrors="1"><Properties action="D" displayDecimal="0" default="0" hive="HKEY_CURRENT_USER" key="Software\Mozilla\Firefox\Launcher" name="C:\Program Files\Mozilla Firefox\firefox.exe|Launcher" type="REG_QWORD" value="0000000000000000"/><Filters/></Registry>
<Registry clsid="{9CD4B2F4-923D-47f5-A062-E897DD1DAD50}" name="C:\Program Files\Mozilla Firefox\firefox.exe|Browser" status="C:\Program Files\Mozilla Firefox\firefox.exe|Browser" image="10" changed="2019-06-26 10:48:51" uid="{E756C79F-EBDC-48ED-8486-1171E668008E}" bypassErrors="1"><Properties action="C" displayDecimal="0" default="0" hive="HKEY_CURRENT_USER" key="Software\Mozilla\Firefox\Launcher" name="C:\Program Files\Mozilla Firefox\firefox.exe|Browser" type="REG_QWORD" value="0000000000000000"/></Registry>
</RegistrySettings>
You can import this XML to GPP by pasting it to User Configuration -> Preferences -> Windows Settings -> Registry
Note: this XML is for Windows x64 and Firefox x64. In case you're running Firefox x86 on Windows x64 the path "C:\Program Files" has to be replaced by "C:\Program Files (x86)"
|
||
Comment 10•5 years ago
|
||
Hey Michael,
First of all, apologies for the late response!
I'm moving this over to a component so developers can take a look at it.
Are the crashes submitted in about:crashes by any chance? If yes, please also post them here, it can be helpful.
Thanks for investigating in depth and providing the details.
|
Reporter | |
Comment 11•5 years ago
|
||
Hi Timea,
since I've found a workaround it wasn't that urgent anymore.
There is no about:crashes available, sorry.
Thanks for taking care.
Regards
Michael
|
||
Comment 12•5 years ago
|
||
(In reply to Timea Babos [on PTO until 19th Aug - ni? Brindusa Tot] from comment #10)
Hey Michael,
First of all, apologies for the late response!
I'm moving this over to a component so developers can take a look at it.
Are the crashes submitted in about:crashes by any chance? If yes, please also post them here, it can be helpful.Thanks for investigating in depth and providing the details.
There is no owner currently for shell integration and this bug doesn't look like a shell integration bug. I'll find a better component
|
|
||
Comment 13•5 years ago
|
||
Aaron, this looks like it might be launcher related
|
|
Reporter | |
Comment 14•5 years ago
|
||
Hi Robert,
thanks for taking care of that issue. I wonder why I'm the only one having it:-)
Maybe mozilla.cfg and/or GPO interferes with startup ... but wait: if I remember correctly I tried without mozilla.cfg and GPO...
As I wrote I was looking for a crash report, but the issue seems to be at a very early stage so no dump. available.
|
||
Comment 17•5 years ago
|
||
Toshihito, could you please try to reproduce this on Nightly?
|
||
Updated•5 years ago
|
|
Assignee | |
Comment 18•5 years ago
•
|
||
I installed the current Nightly (70.0a1) on Windows 1809 x64 by manually running the installer on cmd.exe with SYSTEM. Then I launched firefox.exe both from SYSTEM and a non-Admin user, but no crash.
I also installed the mainline Firefox (68.0.1) in the same way, but not repro either.
Something might be missing in my environment...
|
|
Reporter | |
Comment 19•5 years ago
|
||
Hi Toshihito,
it always worked fine when started from SYSTEM or as an admin.
The non-admin user you were testing never started FF before?
We're using Windows 10 x64 1803, don't know if this makes any difference. Can test next week on 1903.
If required, I can provide our Mozilla.cfg , a dump of our GPO and the installation command we're using.
Michael
|
|
Assignee | |
Comment 20•5 years ago
|
||
I tried Win10 1803 x64 + kb4507466, but no luck.. I installed Firefox with "-S" option on cmd.exe of SYSTEM account, and I created a non-Admin user after installation was done.
Could you please share the installation command and config files? Those would help us understand your environment and repro the issue.
If you still have debuggers in the repro environment, could you also set up Automatic Debugging and reproduce the crash? If this works well, it gives us which exact code crashed.
Configuring Automatic Debugging - Windows applications | Microsoft Docs
("Configuring Automatic Debugging for Application Crashes" secion)
https://docs.microsoft.com/en-us/windows/win32/debug/configuring-automatic-debugging#configuring-automatic-debugging-for-application-crashes
|
||
Updated•5 years ago
|
|
|
Reporter | |
Comment 21•5 years ago
|
||
Installation commands:
Setup.exe /INI=setup.ini
copy override.ini "C:\Program Files\Mozilla Firefox\browser"
copy local-settings.js "C:\Program Files\Mozilla Firefox\browser\defaults\preferences"
copy mozilla.cfg "C:\Program Files\Mozilla Firefox"
Setup.ini:
QuickLaunchShortcut=false
TaskbarShortcut=false
DesktopShortcut=false
MaintenanceService=false
override.ini:
[XRE]
EnableProfileMigrator=false
local-settings.js:
pref("general.config.obscure_value", 0);
pref("general.config.filename", "mozilla.cfg");
mozilla.cfg:
//Firefox Default Settings
// set Firefox Default homepage
defaultPref("browser.startup.homepage", "data:text/plain,browser.startup.homepage=https://companyhomepage ");
// disable default browser check
pref("browser.shell.checkDefaultBrowser", false);
pref("browser.startup.homepage_override.mstone", "ignore");
// disable application updates
pref("app.update.enabled", false);
pref("app.update.service.enabled", false);
// disable extensions updates
pref("extensions.update.enabled", false);
// disable "checking compatibility of add-ons" dialog
pref("extensions.showmismatchUI", false);
// disable search provider updates
pref("browser.search.update", false);
// disables the 'know your rights' button from displaying on first run
pref("browser.rights.3.shown", true);
// disables the request to send performance data from displaying
pref("toolkit.telemetry.prompted", 2);
pref("toolkit.telemetry.rejected", true);
// deactivate internal pdf viewer
pref("pdfjs.disabled",true);
// allow Adobe PDF without prompt for plugin starting with FF29
pref("plugin.state.nppdf", 2);
// disables compatibility check
pref("extensions.checkCompatibility", false);
pref("browser.download.manager.alertOnEXEOpen", true);
pref("browser.download.save_converter_index", 0);
pref("browser.feeds.showFirstRunUI", false);
pref("browser.preferences.advanced.selectedTabIndex", 1);
pref("browser.preferences.lastpanel", 0);
pref("browser.search.selectedEngine", "Google");
pref("startup.homepage_override_url","about:blank");
pref("browser.tabs.warnOnClose", false);
pref("network.cookie.prefsMigrated", true);
pref("browser.newtabpage.enabled",false);
pref("services.sync.prefs.sync.browser.newtabpage.enabled",false);
pref("network.automatic-ntlm-auth.trusted-uris",".company.de,.url1.net,.url2.net,localhost");
pref("network.negotiate-auth.trusted-uris",".company.de,.url1.net,.url2.net,localhost");
// 22-feb-2019 Fix migration problem: FF always starts in privacy mode
lockPref("browser.privatebrowsing.autostart", false);
// disable screen shot utility
lockPref("extensions.screenshots.system-disabled", true);
// disable warning about outdated plugins
lockPref("plugins.hide_infobar_for_outdated_plugin",true);
// do not upload health report
lockPref("datareporting.healthreport.uploadEnabled",false);
// Disable health reporter
lockPref("datareporting.healthreport.service.enabled", false);
// Disable all data upload (Telemetry and FHR)
lockPref("datareporting.policy.dataSubmissionEnabled", false);
// Allow all plugins starting FF 52
lockPref("plugin.load_flash_only", false);
// Disable crash reporter
lockPref("toolkit.crashreporter.enabled", false);
// Disable hardware acceleration added 19.4.2018
lockPref("layers.acceleration.disabled",true);
lockPref("extensions.blocklist.enabled",false);
// disable SSLv3
lockPref("security.tls.version.min",1);
// Heartbeat-Bewertungssystem aus
lockPref("browser.selfsupport.url", "");
// deactivate prefetching
lockPref("network.dns.disablePrefetch",true);
lockPref("network.prefetch-next",false);
// disable Hello
lockPref("loop.enabled",false);
// use Windows certificate store
lockPref("security.enterprise_roots.enabled",true);
// allow opening of local file links on intranet
lockPref("capability.policy.localfilelinks.checkloaduri.enabled", "allAccess");
lockPref("capability.policy.localfilelinks.sites", "https://url");
lockPref("capability.policy.policynames", "localfilelinks");
// Disable Add-ons compatibility checking
clearPref("extensions.lastAppVersion");
// Disable HTML5 Beacons
lockPref("beacon.enabled",false);
// Disable Pocket-API
lockPref("extensions.pocket.enabled",false);
//Disable Safebrowsing
lockPref("browser.safebrowsing.phishing.enabled",false);
lockPref("browser.safebrowsing.malware.enabled",false);
lockPref("browser.safebrowsing.blockedURIs.enabled",false);
lockPref("browser.safebrowsing.downloads.enabled",false);
lockPref("browser.safebrowsing.downloads.remote.enabled",false);
lockPref("browser.safebrowsing.updateURL","");
lockPref("browser.safebrowsing.downloads.remote.url","");
lockPref("extensions.getAddons.cache.enabled",false);
// Disable WebRTC
lockPref("media.peerconnection.enabled",false);
lockPref("loop.enabled",false);
lockPref("loop.facebook.enabled",false);
// Disable reset prompt
lockPref("browser.disableResetPrompt",true);
// FF 60 +
// Network Cookies Lifetime 2 = bis FF geschlossen wird
// lockPref("network.cookie.lifetimePolicy",2);
lockPref("privacy.trackingprotection.enabled", false);
|
|
Reporter | |
Comment 22•5 years ago
|
||
WinDbg Automatic Debugging doesn't work... At least WinDbg never starts on a crash.
|
|
Reporter | |
Comment 23•5 years ago
|
||
Hold your horses ... just tested FireFox 68.0.1 ... no more problems, no more crashes...
Hoping it stays for next 100 versions :-)
|
|
Assignee | |
Comment 24•5 years ago
|
||
Good news! Thank you for letting us know your status.
Also, thank you for providing your configuration files. I deployed all with Firefox 67.0.2 x64 on Win1803, but I still didn't see any problem though the launcher process was enabled. It's also strange Automatic Debugging didn't work.
Hopefully the issue was solved as a part of another bug. If you start to see the issue again, please revisit us.
|
|
||
Comment 25•5 years ago
|
||
Let's resolve this for now. We can always reopen if necessary.
Description
•