Closed Bug 1446214 Opened 7 years ago Closed 7 years ago

Crash in InvalidArrayIndex_CRASH | nsTArray_Impl<T>::ElementAt | static bool `anonymous namespace'::WindowsGamepadService::HandleRawInput

Categories

(Core :: DOM: Device Interfaces, defect)

Unspecified
Windows 10
defect
Not set
critical

Tracking

()

RESOLVED DUPLICATE of bug 1403185

People

(Reporter: mccr8, Unassigned)

Details

(Keywords: crash)

Crash Data

This bug was filed from the Socorro interface and is report bp-a1a67fd5-5d8d-4e37-a747-c61330180314. ============================================================= Top 10 frames of crashing thread: 0 mozglue.dll MOZ_CrashPrintf mfbt/Assertions.cpp:63 1 xul.dll InvalidArrayIndex_CRASH xpcom/ds/nsTArray.cpp:26 2 xul.dll nsTArray_Impl<unsigned char, nsTArrayInfallibleAllocator>::ElementAt xpcom/ds/nsTArray.h:1029 3 xul.dll static bool `anonymous namespace'::WindowsGamepadService::HandleRawInput dom/gamepad/windows/WindowsGamepad.cpp:863 4 xul.dll static __int64 `anonymous namespace'::GamepadWindowProc dom/gamepad/windows/WindowsGamepad.cpp:1000 5 user32.dll UserCallWinProcCheckWow 6 user32.dll DispatchMessageWorker 7 xul.dll static void `anonymous namespace'::DirectInputMessageLoopOnceCallback dom/gamepad/windows/WindowsGamepad.cpp:341 8 xul.dll nsTimerImpl::Fire xpcom/threads/nsTimerImpl.cpp:701 9 xul.dll nsTimerEvent::Run xpcom/threads/TimerThread.cpp:286 ============================================================= Only 3 crashes from a single installation across all branches. ElementAt(aIndex = 117, aLength = 67)
This stack (and weirdly enough, ElementAt call with exact same params) have already been filed as bug 1403185. I'm going to guess this is the same instance. This may be some sort of self built hardware or something?
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → DUPLICATE
Ah, cool. I thought it sounded familiar...
You need to log in before you can comment on or make changes to this bug.