1791287 - Crash in [@ mozilla::net::nsProtocolProxyService::PrefsChanged]

Status: RESOLVED INCOMPLETE

(Core :: Networking, defect, P3)

Description

[Chris Peterson [:cpeterson]]

Crash report: https://crash-stats.mozilla.org/report/index/4583b0d9-cd9d-49e4-9f14-840e90220911

This stack trace looks bogus. All 89 of these crash reports are from one Fenix 105.0b5 user.

Reason: SIGSEGV / SEGV_MAPERR

Top 10 frames of crashing thread:

0 libxul.so mozilla::net::nsProtocolProxyService::PrefsChanged netwerk/base/nsProtocolProxyService.cpp:1052
1 libmozglue.so arena_t::Malloc memory/build/mozjemalloc.cpp:3143
2 libmozglue.so BaseAllocator::malloc memory/build/mozjemalloc.cpp:4288
3 None @0xc2fb49ba 
4 libxul.so XREMain::XRE_main toolkit/xre/nsAppRunner.cpp:5915
5 libxul.so XRE_main toolkit/xre/nsAppRunner.cpp:5975
6 libxul.so GeckoStart toolkit/xre/nsAndroidStartup.cpp:54
7 libxul.so mozilla::BootstrapImpl::GeckoStart toolkit/xre/Bootstrap.cpp:78
8 libmozglue.so Java_org_mozilla_gecko_mozglue_GeckoLoader_nativeRun mozglue/android/APKOpen.cpp:386
9 base.odex base.odex@0x00177d73 

Comment 1

[BugBot [:suhaib / :marco]]

Since the crash volume is low (less than 5 per week), the severity is downgraded to S3. Feel free to change it back if you think the bug is still critical.

For more information, please visit auto_nag documentation.

Comment 2

[Chris Peterson [:cpeterson]]

Crash report: https://crash-stats.mozilla.org/report/index/f4d098f2-0c15-4686-903d-e2a8f0221217

Reason: EXCEPTION_ACCESS_VIOLATION_WRITE

Top 10 frames of crashing thread:

0  xul.dll  mozilla::net::nsProtocolProxyService::PrefsChanged  netwerk/base/nsProtocolProxyService.cpp:1023
1  xul.dll  mozilla::net::nsProtocolProxyService::Init  netwerk/base/nsProtocolProxyService.cpp:793
2  xul.dll  mozilla::xpcom::CreateInstanceImpl  xpcom/components/StaticComponents.cpp:10828
3  xul.dll  mozilla::xpcom::StaticModule::CreateInstance const  xpcom/components/StaticComponents.cpp:13089
3  xul.dll    xpcom/components/nsComponentManager.cpp:184
3  xul.dll  nsComponentManagerImpl::GetServiceLocked  xpcom/components/nsComponentManager.cpp:975
4  xul.dll  nsComponentManagerImpl::GetServiceByContractID  xpcom/components/nsComponentManager.cpp:1164
5  xul.dll  CallGetService  xpcom/components/nsComponentManagerUtils.cpp:61
5  xul.dll  nsGetServiceByContractIDWithError::operator const  xpcom/components/nsComponentManagerUtils.cpp:250
6  xul.dll  nsCOMPtr_base::assign_from_gs_contractid_with_error  xpcom/base/nsCOMPtr.cpp:91

Comment 3

[edgul]

Putting in priority review in case someone wants to take a look at this.
Also putting in monitor in case it doesn't get picked up right away.

Comment 4

[Valentin Gosu [:valentin]]

There are no crashes in recent builds. We'll be monitoring if this still happens.

Comment 5

[Valentin Gosu [:valentin]]

Looking at recent crashes, there are 4 TB 102.7.2 crashes with:
addr:0x00007ffcde6ed885 install date:2023-02-08 15:32:05
and one esr 102.1.0esr 0x0000008b1e1f9ec8 2022-11-29 16:03:23

I also suspect faulty hardware.

Comment 6

[Kershaw Chang [:kershaw]]

The recent spikes on 2023-09-29 were all from the same user, just like the reports on 2023-09-19.
As comment #5 said, I agree this seems to be caused by faulty hardware.

I think we can close this bug.