Latest Firefox Nightly does not open in Windows 10
Categories
(Firefox :: Untriaged, defect)
Tracking
()
People
(Reporter: veeven, Unassigned)
References
Details
Attachments
(1 file)
23.54 KB,
image/png
|
Details |
User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:83.0) Gecko/20100101 Firefox/83.0
Steps to reproduce:
I received an auto-update on Nightly. And, I restared to complete the update.
Actual results:
Upon restart, Nightly didn't start. Instead, the following dialog has shown (see attachment, below text copy):
[Window Title]
Firefox Nightly[Main Instruction]
Firefox Nightly has stopped working[Content]
A problem caused the program to stop working correctly. Please close the program.[Close the program]
Expected results:
Nightly should have opened without showing an error.
The build ID I could successfully launch Nightly is this: 20201009041754
Comment 1•4 years ago
|
||
Are you using a registered windows?
Updated•4 years ago
|
Comment 3•4 years ago
|
||
@Veeven
Do you see any detail on the error? I have at least a couple of people reporting a similar issue over the weekend (bug 1670537).
(In reply to Francesco Lodolo [:flod] from comment #3)
@Veeven
Do you see any detail on the error? I have at least a couple of people reporting a similar issue over the weekend (bug 1670537).
Even when I start from the command line, I couldn't see any errors. It just opens the error dailog (attached earlier).
Here's the entry from Windows Event Viewer:
Faulting application name: firefox.exe, version: 83.0.0.7587, time stamp: 0x5f80ecd5
Faulting module name: xul.dll, version: 83.0.0.7587, time stamp: 0x5f80ecfa
Exception code: 0x80000003
Fault offset: 0x0000000000a63e7a
Faulting process id: 0x448c
Faulting application start time: 0x01d6a0907826f7b4
Faulting application path: C:\Users\<snip>\apps\firefox-nightly\firefox.exe
Faulting module path: C:\Users\<snip>\apps\firefox-nightly\xul.dll
Report Id: 93a7f643-8e64-4125-af4f-5b0a2cfafed9
Faulting package full name:
Faulting package-relative application ID:
Seems it is same as reported in the bug 1670537
Updated•4 years ago
|
Updated•4 years ago
|
Description
•