Closed Bug 1726641 Opened 3 years ago Closed 3 years ago

Crash in [@ InvalidArrayIndex_CRASH | mozilla::net::nsSocketTransportService::UpdatePrefs]

Categories

(Core :: Networking, defect, P3)

Product:
Core
Component:
Networking
Platform:
Unspecified
Android
Type:
defect

Tracking

()

Status:
RESOLVED WORKSFORME

People

(Reporter: mccr8, Unassigned)

Details

(Keywords: crash, Whiteboard: [necko-triaged])

Crash Data

Crash report: https://crash-stats.mozilla.org/report/index/36d05ef3-9256-466d-99ad-1286e0210818

MOZ_CRASH Reason: ElementAt(aIndex = 4294967295, aLength = 4058358894)

Top 10 frames of crashing thread:

0 libxul.so InvalidArrayIndex_CRASH xpcom/ds/nsTArray.cpp:28
1 libxul.so mozilla::net::nsSocketTransportService::UpdatePrefs netwerk/base/nsSocketTransportService2.cpp:1485
2  @0xc340157e 
3 libxul.so mozilla::detail::nsTStringRepr<char>::Equals const xpcom/string/nsTSubstring.cpp:981
4 dalvik-main space (region space)_2713_2713 (deleted) dalvik-main space @0x22726234 
5 dalvik-main space (region space)_2713_2713 (deleted) dalvik-main space @0x23a52d64 
6 dalvik-main space (region space)_2713_2713 (deleted) dalvik-main space @0x216d6260 
7 dalvik-main space (region space)_2713_2713 (deleted) dalvik-main space @0x1a736262 
8 dalvik-main space (region space)_2713_2713 (deleted) dalvik-main space @0x24a2352b 
9 dalvik-main space (region space)_2713_2713 (deleted) dalvik-main space @0x20736262

41 crashes, but all from a single installation. From where the crash is, maybe somebody has network.socket.forcePort set to a bizarre value that is causing an issue?

Severity: -- → S2

I think we can ignore this for now, since all crashes are from the same installation.

Severity: S2 → S3
Priority: -- → P3
Whiteboard: [necko-triaged]

Closing because no crashes reported for 12 weeks.

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.