1457615 - Crashfirefox64.exe crashes Firefox but does not generate a Crash Report.

Status: NEW

(Toolkit :: Crash Reporting, defect)

Description

[Trevor Skywalker]

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/

Comment 1

[Trevor Skywalker]

Attachment: screenshot.2018-04-14 (164).jpg

Comment 2

[Trevor Skywalker]

Attachment: screenshot.2018-04-14 (169).jpg

Comment 3

[Trevor Skywalker]

Attachment: screenshot.2018-04-14 (170).jpg

Comment 4

[Trevor Skywalker]

Attachment: screenshot.2018-04-14 (178).jpg

Comment 5

[Gabriele Svelto [:gsvelto] (PTO)]

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?

Comment 6

[Trevor Skywalker]

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)

Comment 7

[Trevor Skywalker]

Attachment: 1525143654.jpg

Comment 8

[Trevor Skywalker]

Attachment: 1525143894.jpg

Comment 9

[Trevor Skywalker]

Attachment: 1525144016.jpg

Comment 10

[Trevor Skywalker]

Attachment: 1525144029.jpg

Comment 11

[Trevor Skywalker]

Attachment: screenshot 2018-04-30 (1).jpg

Comment 12

[Trevor Skywalker]

(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

Comment 13

[Trevor Skywalker]

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).

Comment 14

[Trevor Skywalker]

Attachment: screenshot 2018-05-04 (23) - (49) PDF.pdf

Comment 15

[Trevor Skywalker]

Attachment: screenshot 2018-05-04 (24).jpg

Comment 16

[Trevor Skywalker]

Attachment: screenshot 2018-05-04 (27).jpg

Comment 17

[Trevor Skywalker]

Attachment: screenshot 2018-05-04 (29).jpg

Comment 18

[Trevor Skywalker]

Attachment: screenshot 2018-05-04 (49).jpg

Comment 19

[Gabriele Svelto [:gsvelto] (PTO)]

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

[Wayne Mery (:wsmwk)]

gsvelto,
Trevor's account is disabled, so it is unclear you will have a reply to your question in  comment 19

Comment 21

[Gabriele Svelto [:gsvelto] (PTO)]

Nevermind, I'll have to revisit this anyway for the AArch64 builds.

Comment 22

[Gian-Carlo Pascutto [:gcp]]

Don't think this warrants S2.