1862518 - minidump generation and symbol generation seem to disagree on macOS

Status: NEW

(Toolkit :: Crash Reporting, defect)

Description

[Gabriele Svelto [:gsvelto]]

Yesterday I was testing a local build on macOS/AArch64 and noticed that I couldn't symbolicate the crashes my build generated, even though the symbols were built at the same time as the binaries. The only explanation is that the debug identifiers generated by the minidump writer differ from those generated by dump_syms when emitting symbol files.

I have the feeling that this problem might be specific to local builds, because if it was happening on release ones we'd have noticed already. It would have caused a very large influx of unsymbolicated crash reports.

Comment 1

[:Gijs (away/busy until Mar 10)]

(In reply to Gabriele Svelto [:gsvelto] from comment #0)

I have the feeling that this problem might be specific to local builds, because if it was happening on release ones we'd have noticed already. It would have caused a very large influx of unsymbolicated crash reports.

How quickly would we notice if this was a recent regression and was happening on nightly builds only (so far)? Or do you mean "shippable/shipped-to-users" when you say "release" ? :-)

Comment 2

[Gabriele Svelto [:gsvelto]]

We'd see it within 24 hours; the crash spike detector works on a per-channel basis and it would pick up new unsymbolicated signatures right away, so we'd notice very quickly.

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.