Open
Bug 1457615
Opened 7 years ago
Updated 1 year ago
Crashfirefox64.exe crashes Firefox but does not generate a Crash Report.
Categories
(Toolkit :: Crash Reporting, defect)
Tracking
()
NEW
People
(Reporter: skywalker333, Unassigned)
References
(Blocks 1 open bug, )
Details
(Keywords: crash, hang)
Attachments
(14 files)
(deleted),
image/jpeg
|
Details | |
(deleted),
image/jpeg
|
Details | |
(deleted),
image/jpeg
|
Details | |
(deleted),
image/jpeg
|
Details | |
(deleted),
image/jpeg
|
Details | |
(deleted),
image/jpeg
|
Details | |
(deleted),
image/jpeg
|
Details | |
(deleted),
image/jpeg
|
Details | |
(deleted),
image/jpeg
|
Details | |
(deleted),
application/pdf
|
Details | |
(deleted),
image/jpeg
|
Details | |
(deleted),
image/jpeg
|
Details | |
(deleted),
image/jpeg
|
Details | |
(deleted),
image/jpeg
|
Details |
Crashfirefox64.exe crashes Firefox but does not generate a Crash Report.
Sometimes Windows Error Reporting seems to "take over" the diagnostics and troubleshooting processes and may be blocking crashfirefox64.exe from doing it's job.
Windows Error Reporting will generate minidump files for analysis, and asks the user if they want to Send the information to Microsoft to help in troubleshooting the problem. It doesn't offer any option to send the information to Firefox. A local copy of the data is stored in %appdata%\Local\Temp. It may be preventing crashfirefox64.exe from accessing the relevant crash data.
C:\Users\<username>\AppData\Local\Temp\
WERD5EA.tmp.hdmp
WERCF45.tmp.appcompat.txt
WER5303.tmp.WERInternalMetadata.xml
I've experimented with manually closing (killing) Windows Error Reporting (WERfault.exe) via Windows Task Manager/Resource Monitor but that doesn't help. Crashfirefox still does not generate a crash report.
I've experimented with disabling Windows Error Reporting for the firefox.exe process (specifically by adding it to the list of exemptions). I still don't get a crash report. Windows just closes firefox and crashfirefox doesn't seem to do anything.
https://ftp.mozilla.org/pub/utilities/crashfirefox-intentionally/
Reporter | ||
Comment 1•7 years ago
|
||
Reporter | ||
Comment 2•7 years ago
|
||
Reporter | ||
Comment 3•7 years ago
|
||
Reporter | ||
Comment 4•7 years ago
|
||
Reporter | ||
Updated•7 years ago
|
Comment 5•7 years ago
|
||
This shouldn't be happening unless crash reporting is explicitly disabled in Firefox or if the crash is among those we're unable to catch. Which version of Firefox did you experience this issue on?
Reporter | ||
Comment 6•7 years ago
|
||
I haven't explicitly disabled crash reporting. Crash reporting is enabled and works as expected when I am shutting down, restarting or updating Firefox.
I use crashfirefox for when Firefox is hung and not responding.
I'm currently using FF Nightly 61.0a1 (2018-04-30) (64-bit)
Reporter | ||
Comment 7•7 years ago
|
||
Reporter | ||
Comment 8•7 years ago
|
||
Reporter | ||
Comment 9•7 years ago
|
||
Reporter | ||
Comment 10•7 years ago
|
||
Reporter | ||
Comment 11•7 years ago
|
||
Reporter | ||
Comment 12•7 years ago
|
||
(In reply to Gabriele Svelto [:gsvelto] from comment #5)
> This shouldn't be happening unless crash reporting is explicitly disabled in
> Firefox or if the crash is among those we're unable to catch. Which version
> of Firefox did you experience this issue on?
I've experienced this issue on Firefox versions:
61.0a1 (64-bit) Nightly
60.0b16 (64-bit) Beta
59.0.3 (64-bit) Release
Reporter | ||
Comment 13•7 years ago
|
||
Now I'm experiencing this issue but sometimes instead of Windows Error Reporting generating minidumps and offering to send the data to Microsoft for analysis it just offers to close the program.
Error Message:
Firefox has stopped working
A problem caused the program to stop working correctly. Windows will close the program and notify you if a solution is available.
"Close Program" (only option).
Reporter | ||
Comment 14•7 years ago
|
||
Reporter | ||
Comment 15•7 years ago
|
||
Reporter | ||
Comment 16•7 years ago
|
||
Reporter | ||
Comment 17•7 years ago
|
||
Reporter | ||
Comment 18•7 years ago
|
||
Comment 19•7 years ago
|
||
Thanks, I had missed the fact that Firefox was hung when you tried to crash it. Depending on how it got hung the exception handler might not be able to execute either thus causing WER to take over. What caused the hang in the first place?
Comment 20•6 years ago
|
||
gsvelto,
Trevor's account is disabled, so it is unclear you will have a reply to your question in comment 19
Flags: needinfo?(gsvelto)
Updated•6 years ago
|
Flags: needinfo?(gsvelto)
Comment 21•6 years ago
|
||
Nevermind, I'll have to revisit this anyway for the AArch64 builds.
Updated•2 years ago
|
Severity: major → S2
You need to log in
before you can comment on or make changes to this bug.
Description
•