Closed Bug 1433418 Opened 2 years ago Closed 2 years ago

Crash in SharedLibraryAtPath

Categories

(Core :: mozglue, defect, critical)

Unspecified
Android
defect
Not set
critical

Tracking

()

RESOLVED WORKSFORME
Tracking Status
firefox-esr52 --- unaffected
firefox-esr60 --- unaffected
firefox58 --- unaffected
firefox59 --- unaffected
firefox60 --- wontfix
firefox61 --- fixed

People

(Reporter: calixte, Unassigned)

References

(Blocks 1 open bug)

Details

(Keywords: crash, regression, topcrash)

Crash Data

This bug was filed from the Socorro interface and is
report bp-1f0c2434-1bb4-49fa-b9ee-c95150180126.
=============================================================

Top 10 frames of crashing thread:

0 libc.so libc.so@0x1098c 
1 libxul.so SharedLibraryAtPath tools/profiler/core/shared-libraries-linux.cc:65
2 libxul.so wcsrtombs 
3 libmozglue.so MOZ_Z_crc32_combine_ modules/zlib/src/crc32.c:353
4 libmozglue.so arena_t::SplitRun memory/build/rb.h:150
5 libmozglue.so arena_t::DallocRun memory/build/rb.h:150
6 libxul.so std::__ndk1::__split_buffer<unsigned int, std::__ndk1::allocator<unsigned int>&>::__split_buffer android-ndk/sources/cxx-stl/llvm-libc++/include/__split_buffer:314
7 libxul.so nsTSubstring<char16_t>::Assign xpcom/string/nsTSubstring.cpp:440
8 libxul.so std::__ndk1::__split_buffer<unsigned int, std::__ndk1::allocator<unsigned int>&>::__split_buffer android-ndk/sources/cxx-stl/llvm-libc++/include/__split_buffer:314
9 libxul.so nsTString<char16_t>::nsTString xpcom/string/nsTSubstring.cpp:538

=============================================================

There is 1 crash (from 1 installation) in nightly 60 with buildid 20180126035134. In analyzing the backtrace, the regression may have been introduced by patch [1] to fix bug 1414506.

[1] https://hg.mozilla.org/mozilla-central/rev?node=3b862e2b9e0b
Flags: needinfo?(mh+mozilla)
After waiting a bit to see if more crashes come in, it seems all of them are with android version < 6. There's even one on API level 19, which is < 5, and that's not even supposed to have dl_iterate_phdr, so that should be using the old code.

Can we reproduce those, with more significant stack traces? Eugen, could you look into this?
Flags: needinfo?(mh+mozilla) → needinfo?(esawin)
While we're waiting for the answer, this is low volume, making it fix-optional.
This is the number 1 top Nightly crash on Android for 4-17, with almost no repeat install times.
Keywords: topcrash
Looking through some recent crashes, I found some reports that have non-trivial stack traces:
  bp-c5d3645d-a1a9-43d2-b995-c9b3e0180420
  bp-59d59aac-b12f-40f0-84cf-612690180420

The crash rate seems to have increased in the last week.

David, is there somebody who could look at this? Thanks.
Flags: needinfo?(dbolter)
Recent build crashes I looked up builds from the last few days. Crashes were all on Android API versions 19-22. (22 is Android 5.1/Lollipop I think)..

Snorp any ideas?
Flags: needinfo?(snorp)
Flags: needinfo?(sdaswani)
Flags: needinfo?(dbolter)
I'll wait for snorp to comment before handing it off to the Softvision dev crew.
Starting with the 4-28 build I don't see any of these crashes on nightly.
Interesting. Possibly the same as bug 1455662?
Flags: needinfo?(snorp)
(In reply to Marcia Knous [:marcia - needinfo? me] from comment #9)
> Starting with the 4-28 build I don't see any of these crashes on nightly.

It may be moved to bug 1458193.
Clearing my NI, please NI again if I'm needed here.
Flags: needinfo?(sdaswani)
Comment 9 still holds. I don't think leaving this bug open is serving much purpose at this point.
Status: NEW → RESOLVED
Closed: 2 years ago
Flags: needinfo?(esawin)
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.