Closed Bug 1187953 Opened 6 years ago Closed 3 years ago

Crashes on Motorola RAZRi with no usable stack

Categories

(Toolkit :: Crash Reporting, defect)

x86
Android
defect
Not set
critical

Tracking

()

RESOLVED WONTFIX

People

(Reporter: gcp, Unassigned)

Details

(Keywords: crash)

Crash Data

This bug was filed from the Socorro interface and is 
report bp-401e58fb-df2a-4b56-a102-550ce2150727.
=============================================================
I'm seeing this often when browsing with Aurora on a Motorola RaZRi, Android 4.1.x, x86.

Unfortunately no stacks, nothing in the log, and the crash address varies :-(
Summary: crash in @0x5f67eacc → Crashes on Motorola RAZRi with varfying address & no usable stack
Summary: Crashes on Motorola RAZRi with varfying address & no usable stack → Crashes on Motorola RAZRi with varying address & no usable stack
Crash Signature: [@ @0x5f67eacc] → [@ @0x5f67eacc] [@ @0x5f44d20c]
Summary: Crashes on Motorola RAZRi with varying address & no usable stack → Crashes on Motorola RAZRi with no usable stack
Ted or Kairo are we uploading the x86 Android build debug symbols? If you don't know please forward to someone on the build infrastructure team.
tracking-fennec: ? → ---
Flags: needinfo?(ted)
Flags: needinfo?(kairo)
Product: Firefox for Android → Socorro
Flags: needinfo?(ted)
This isn't about symbols, this report is showing that is has no modules (check the modules tab), so it can't even associate code addresses with code modules.
Flags: needinfo?(kairo)
stderr from minidump_stackwalk shows:
2015-08-11 07:06:22: minidump.cc:2557: ERROR: MinidumpModuleList could not store module 186/188, libnss3.so, 0x57f27000+0x287000

...which indicates that we've got a problem with the entries in the module list here.
Try to set MOZ_LINKER_ONDEMAND to 0 in the environment and see if that still happens then.
From /proc/self/maps inside the minidump (you can see this with minidump_dump):
57c3c000-57f27000 rw-s 00000000 00:04 49004      /dev/ashmem/libnss3.so (deleted)
57f27000-57f63000 r-xs 00000000 00:04 49004      /dev/ashmem/libnss3.so (deleted)
57f63000-57f67000 ---s 0003c000 00:04 49004      /dev/ashmem/libnss3.so (deleted)
57f67000-57fab000 r-xs 00040000 00:04 49004      /dev/ashmem/libnss3.so (deleted)
57fab000-57faf000 ---s 00084000 00:04 49004      /dev/ashmem/libnss3.so (deleted)
57faf000-57fbf000 r-xs 00088000 00:04 49004      /dev/ashmem/libnss3.so (deleted)
57fbf000-57fc3000 ---s 00098000 00:04 49004      /dev/ashmem/libnss3.so (deleted)
57fc3000-5800b000 r-xs 0009c000 00:04 49004      /dev/ashmem/libnss3.so (deleted)
5800b000-5800f000 ---s 000e4000 00:04 49004      /dev/ashmem/libnss3.so (deleted)
5800f000-58077000 r-xs 000e8000 00:04 49004      /dev/ashmem/libnss3.so (deleted)
58077000-5807f000 ---s 00150000 00:04 49004      /dev/ashmem/libnss3.so (deleted)
5807f000-5808f000 r-xs 00158000 00:04 49004      /dev/ashmem/libnss3.so (deleted)
5808f000-58093000 ---s 00168000 00:04 49004      /dev/ashmem/libnss3.so (deleted)
58093000-580df000 r-xs 0016c000 00:04 49004      /dev/ashmem/libnss3.so (deleted)
580df000-580e3000 ---s 001b8000 00:04 49004      /dev/ashmem/libnss3.so (deleted)
580e3000-580ef000 r-xs 001bc000 00:04 49004      /dev/ashmem/libnss3.so (deleted)
580ef000-5819d000 ---s 001c8000 00:04 49004      /dev/ashmem/libnss3.so (deleted)
5819e000-581ab000 rw-s 00276000 00:04 49004      /dev/ashmem/libnss3.so (deleted)

It's barfing on adding libnss3 after the /dev/ashmem mapping:
133,/dev/ashmem/libnss3.so (deleted),0x57c3c000,0x561000
186,libnss3.so,0x57f27000,0x287000

Humorously, Breakpad has a special-case for /dev/ashmem mappings, but it only works the other way (if an ashmem mapping conflicts with an existing mapping):
https://code.google.com/p/google-breakpad/source/browse/trunk/src/processor/minidump.cc#2550
Breakpad is supposed to be fed with report_mapping for those.
https://dxr.mozilla.org/mozilla-central/source/mozglue/linker/CustomElf.cpp#222
Component: General → Symbols
Component: Symbols → Breakpad Integration
Product: Socorro → Toolkit
Closing because no crash reported since 12 weeks.
Status: NEW → RESOLVED
Closed: 3 years ago
Resolution: --- → WONTFIX
Closing because no crash reported since 12 weeks.
You need to log in before you can comment on or make changes to this bug.