Open Bug 1681846 Opened 1 year ago Updated 1 year ago

Missing MOZ_CRASH reason in crash reports from Android, take two


(Toolkit :: Crash Reporting, defect, P2)





(Reporter: mstange, Unassigned, NeedInfo)


This is a follow-up bug to bug 1666383, which did not fix the bug for me.

Steps to reproduce:

  1. In Firefox for Android, navigate to about:crashcontent.
  2. Alternatively, in a build before bug 1681842 appeared, navigate to about:crashparent.

Expected results:
The Socorro crash report for that crash should include a Moz crash reason.

Actual results:
No moz crash reason can be found.

Example reports:

I can't reproduce in the emulator so this must have something to do with the environment we have on the phones. I'm wondering if SELinux might be interfering with the code we run in the exception handler? That would also explain bug 1681842 which I also cannot reproduce in the emulator. One thing I noticed while inspecting some crashes is that some other fields are also missing: the StackTraces field, the Telemetry* as well as the ContentSandbox* ones.

Assignee: nobody → gsvelto
Severity: -- → S2
Priority: -- → P1

This is only happening on ARM, I verified only the 32-bit build but I'll try the 64- one too. On x86-64 - which is what we use for the emulator - the issue doesn't repro.

Hardware: All → ARM

I smell a compiler issue: if I put a print statement in AnnotateMozCrashReason() everything works as advertised, if I remove it then the gMozCrashReason variable is never assigned the string passed to MOZ_CRASH(). The fact that this only happens on ARM and not on x86-64 makes me doubly suspicious about the compiler. Lowering the priority given that I don't have time to investigate into clang ATM.

Assignee: gsvelto → nobody
Priority: P1 → P2

See the comment above

Flags: needinfo?(mh+mozilla)
You need to log in before you can comment on or make changes to this bug.