Closed
Bug 1187953
Opened 9 years ago
Closed 6 years ago
Crashes on Motorola RAZRi with no usable stack
Categories
(Toolkit :: Crash Reporting, defect)
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. =============================================================
Reporter | ||
Comment 1•9 years ago
|
||
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 :-(
Reporter | ||
Updated•9 years ago
|
Summary: crash in @0x5f67eacc → Crashes on Motorola RAZRi with varfying address & no usable stack
Reporter | ||
Updated•9 years ago
|
Summary: Crashes on Motorola RAZRi with varfying address & no usable stack → Crashes on Motorola RAZRi with varying address & no usable stack
Reporter | ||
Comment 2•9 years ago
|
||
https://crash-stats.mozilla.com/report/index/1a72476a-2932-4394-9baf-8372d2150808 https://crash-stats.mozilla.com/report/index/7c22b75a-56f4-47d6-8c96-397e62150806 https://crash-stats.mozilla.com/report/index/78a071e0-e483-4ce4-b3ce-a94652150801 https://crash-stats.mozilla.com/report/index/1df4234b-2c91-4125-9b13-533892150801 https://crash-stats.mozilla.com/report/index/6176b248-4970-4729-8519-3e81b2150801 Fennec is almost unusable on this device.
tracking-fennec: --- → ?
Reporter | ||
Updated•9 years ago
|
Crash Signature: [@ @0x5f67eacc] → [@ @0x5f67eacc]
[@ @0x5f44d20c]
Reporter | ||
Updated•9 years ago
|
Summary: Crashes on Motorola RAZRi with varying address & no usable stack → Crashes on Motorola RAZRi with no usable stack
Comment 3•9 years ago
|
||
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
Updated•9 years ago
|
Flags: needinfo?(ted)
Comment 4•9 years ago
|
||
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)
Comment 5•9 years ago
|
||
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.
Comment 6•9 years ago
|
||
Try to set MOZ_LINKER_ONDEMAND to 0 in the environment and see if that still happens then.
Comment 7•9 years ago
|
||
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
Comment 8•9 years ago
|
||
Breakpad is supposed to be fed with report_mapping for those. https://dxr.mozilla.org/mozilla-central/source/mozglue/linker/CustomElf.cpp#222
Updated•8 years ago
|
Component: General → Symbols
Updated•8 years ago
|
Component: Symbols → Breakpad Integration
Product: Socorro → Toolkit
Comment 9•6 years ago
|
||
Closing because no crash reported since 12 weeks.
Status: NEW → RESOLVED
Closed: 6 years ago
Resolution: --- → WONTFIX
Comment 10•6 years ago
|
||
Closing because no crash reported since 12 weeks.
You need to log in
before you can comment on or make changes to this bug.
Description
•