964368 - Some crashes not being caught after background update on Windows?

Status: RESOLVED WORKSFORME

(Toolkit :: Crash Reporting, defect)

Description

[(not currently active) Ted Mielczarek]

I've seen a few instances of crashes on my Windows nightly that gave me the Windows error dialog instead of our crash reporter. Attaching a debugger generally showed that the crash itself was pretty uninteresting. The latest one was a simple OOM crash. This hasn't happened very often, but I've seen it at least 3 times locally.

I'm wondering if this is something that's happening more regularly? I don't know if there's anything interesting about the way we rename the files out from under the running Firefox binary that could cause this.

I can always tell when this happens because the module names in the debugger are like "firefox\tobedeleted\mozXXXX.tmp". It's probably possible for us to run an analysis against the Windows Error Reporting reports we get to find out if this situation is happening frequently.

Comment 1

[Jens Stutte [:jstutte]]

Moving this to Crash Reporting mostly because I hope that someone there is able to say if this is still relevant.

Comment 2

[Gian-Carlo Pascutto [:gcp]]

This may not be easy to test, but on the positive side, the crashes that end up in WER should eventually make it back to our own crash reporting machinery.

Comment 3

[BugBot [:suhaib / :marco/ :calixte]]

The severity field is not set for this bug.
:gsvelto, could you have a look please?

For more information, please visit BugBot documentation.

Comment 4

[Gabriele Svelto [:gsvelto]]

I haven't seen this happen in a while, and given that WER stays in place until the very last moment these would be likely caught by our machinery anyway. I'm inclined to close this as WORKSFORME and open a new bug if we detect a new instance where we're missing crashes.