Closed
Bug 1695059
Opened 3 years ago
Closed 3 years ago
Crash in [@ mozilla::java::GeckoAppShell::GetNetworkLinkType]
Categories
(GeckoView :: General, defect, P1)
Tracking
(Not tracked)
RESOLVED
WORKSFORME
People
(Reporter: RyanVM, Unassigned)
References
Details
(Keywords: crash, Whiteboard: [geckoview:m89])
Crash Data
+++ This bug was initially created as a clone of Bug #1694179 +++
This is for the original issue covered in bug 1694179 prior to the regression in the 25-Feb Nightly build caused by https://github.com/mozilla-mobile/fenix/issues/18177.
Crash report: https://crash-stats.mozilla.org/report/index/d0659b12-d974-46aa-b759-c4a6a0210222
Reason: SIGSEGV /SEGV_MAPERR
Top 10 frames of crashing thread:
0 libxul.so mozilla::java::GeckoAppShell::GetNetworkLinkType widget/android/GeneratedJNIGeckoAppShellWrappers.cpp:311
1 libxul.so nsAndroidNetworkLinkService::GetLinkType netwerk/system/android/nsAndroidNetworkLinkService.cpp:120
2 libxul.so mozilla::net::nsHttpChannel::OpenCacheEntryInternal netwerk/protocol/http/nsHttpChannel.cpp:3844
3 libxul.so mozilla::net::nsHttpChannel::ConnectOnTailUnblock netwerk/protocol/http/nsHttpChannel.cpp:777
4 libxul.so mozilla::net::nsHttpChannel::ContinueOnBeforeConnect netwerk/protocol/http/nsHttpChannel.cpp:714
5 libxul.so mozilla::net::nsHttpChannel::OnBeforeConnect netwerk/protocol/http/nsHttpChannel.cpp:611
6 libxul.so mozilla::net::nsHttpChannel::HandleOnBeforeConnect netwerk/protocol/http/nsHttpChannel.cpp:513
7 libxul.so std::__ndk1::__function::__func<mozilla::net::nsHttpChannel::HandleOnBeforeConnect /builds/worker/fetches/android-ndk/sources/cxx-stl/llvm-libc++/include/functional:1651
8 libxul.so mozilla::net::nsHttpChannel::CallOrWaitForResume netwerk/protocol/http/nsHttpChannel.cpp:9326
9 libxul.so mozilla::detail::RunnableFunction<mozilla::net::nsHttpChannel::Resume xpcom/threads/nsThreadUtils.h:534
Updated•3 years ago
|
Priority: P2 → P1
Updated•3 years ago
|
Rank: 1
Comment 1•3 years ago
|
||
This crash hasn't happened in Nightly since March 6th, I'm pretty sure we can call it fixed. (maybe from Bug 1694179?)
Status: NEW → RESOLVED
Closed: 3 years ago
Resolution: --- → WORKSFORME
You need to log in
before you can comment on or make changes to this bug.
Description
•