Crash in [@ <unknown in libxul.so>] on Android
Categories
(Toolkit :: Crash Reporting, defect)
Tracking
()
People
(Reporter: fluffyemily, Unassigned)
References
Details
(Keywords: crash)
Crash Data
Crash report: https://crash-stats.mozilla.org/report/index/1d42fc42-f88b-4ced-afe9-952f90210819
Reason: SIGILL / ILL_ILLOPC
Top 10 frames of crashing thread:
0 @0x7451d0ec80
1 @0x7451c9ad6c
2 libxul.so <unknown in libxul.so>
3 libxul.so mozilla::net::nsHttpChannel::QueryInterface netwerk/protocol/http/nsHttpChannel.cpp:5341
4 libxul.so js::InternalCallOrConstruct js/src/vm/Interpreter.cpp:521
5 libxul.so mozilla::dom::ipc::StructuredCloneData::Write dom/ipc/StructuredCloneData.cpp:121
6 libxul.so XPCNativeInterface::GetNewOrUsed js/xpconnect/src/XPCWrappedNativeInfo.cpp:130
7 libxul.so XPCConvert::NativeInterface2JSObject js/xpconnect/src/XPCConvert.cpp:935
8 libxul.so JS_CallFunctionValue js/src/vm/CallAndConstruct.cpp:53
9 libxul.so <unknown in libxul.so>
Reporter | ||
Comment 1•4 years ago
|
||
Can you help us figure out this issue?
Comment 2•4 years ago
|
||
Bug 1725990 got filed on working around this, but it sounded like gsvelto thought that maybe that wasn't the right approach here?
Updated•4 years ago
|
Comment 3•4 years ago
|
||
I should have a fix ready by next week that correctly labels the executable sections of libxul that don't have symbols (such as the procedure linkage table). It should make these signatures saner though not necessarily more actionable.
Comment hidden (Intermittent Failures Robot) |
Comment 5•4 years ago
|
||
Now that bug 1725990 landed we should have a signature change here. NI? myself to check and add it later.
Comment 6•4 years ago
|
||
Due to a mistake in bug 1725990 the resulting crash signatures are still garbage (Socorro has a rule to ignore symbols between angle brackets unless they fall within certain conditions) so I'm filing another bug to solve the issue.
Comment 7•3 years ago
|
||
Gabriele, looks like this still isn't fixed by the other bugs? :-(
Comment 8•3 years ago
|
||
Crashes are only coming from ancient versions of Firefox, not much we can do here.
Description
•