New issue
Advanced search Search tips

Issue 821155 link

Starred by 1 user
Status: WontFix
Owner: ----
Closed: Dec 21
Components:
EstimatedDays: ----
NextAction: ----
OS: Android
Pri: 2
Type: Bug



Sign in to add a comment

Crash in ProxyConfigServiceAndroid while initializing RequestContext.

Project Member Reported by kapishnikov@chromium.org, Mar 12 2018 
********** Crash dump: **********
Build fingerprint: 'motorola/panell_21_d/panell_d:7.0/NRD90M.03.038/038:user/release-keys'
pid: 5570, tid: 5627, name: CronetInit
signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 0x3ada2740
Stack frame #00 pc 0018b692  arm/libcronet.66.0.3348.3.so (offset 0xbe000): Routine net::ProxyConfigServiceAndroid::ProxyConfigServiceAndroid(scoped_refptr<base::SequencedTaskRunner> const&, scoped_refptr<base::SequencedTaskRunner> const&) at net/proxy_resolution/proxy_config_service_android.cc:363
Stack frame #01 pc 0018dbe7  arm/libcronet.66.0.3348.3.so (offset 0xbe000): Routine std::__ndk1::__unique_if<net::ProxyConfigServiceAndroid>::__unique_single std::__ndk1::make_unique<net::ProxyConfigServiceAndroid, scoped_refptr<base::SequencedTaskRunner> const&, scoped_refptr<base::SingleThreadTaskRunner> >(scoped_refptr<base::SequencedTaskRunner> const&, scoped_refptr<base::SingleThreadTaskRunner>&&) at third_party/android_ndk/sources/cxx-stl/llvm-libc++/include/memory:3026
Stack frame #02 pc 000c1cb9  arm/libcronet.66.0.3348.3.so (offset 0xbe000): Routine cronet::CreateProxyConfigService(scoped_refptr<base::SequencedTaskRunner> const&) at components/cronet/android/cronet_library_loader.cc:147
Stack frame #03 pc 001f4e51  arm/libcronet.66.0.3348.3.so (offset 0xbe000): Routine cronet::CronetURLRequestContext::InitRequestContextOnInitThread() at components/cronet/cronet_url_request_context.cc:224
Stack frame #04 pc 000c3ac1  arm/libcronet.66.0.3348.3.so (offset 0xbe000): Routine Java_org_chromium_net_impl_CronetUrlRequestContext_nativeInitRequestContextOnInitThread at /b/build/slave/cronet-arm/build/src/out/Release/gen/components/cronet/android/cronet_jni_headers/cronet/jni/CronetUrlRequestContext_jni.h:245

Internal bug: b/74474908

Comment 2 by kapishnikov@chromium.org, Mar 12 2018 

Looks like the regression was introduced between 65.0.3325.38 and 66.0.3348.3.

The first change was merged to 65.0.3319.0, so it should not cause the issue.

Comment 3 by pauljensen@chromium.org, Mar 13 2018 

@kapishnikov: is comment 2 still accurate given b/74474908#comment11 ?

Comment 4 by kapishnikov@chromium.org, Mar 13 2018 

It may still be accurate but with less certainty. It is possible that the issue existed before 65.0.3325.38 but reported differently (different PC and offset). I couldn't find any other bugs with the given crash stack, so I would assume that the problem appeared recently and changes between 65.0.3325.38 and 66.0.3348.3 are the first candidates to look at.

Comment 5 by mef@chromium.org, Dec 21

Status: WontFix (was: Untriaged)
Original internal b/74474908 is wontfixed as not reproducible.
►

Sign in to add a comment