Closed
Bug 1312937
Opened 8 years ago
Closed 8 years ago
Crash in InvalidArrayIndex_CRASH | mozilla::InactiveRefreshDriverTimer::TickOne
Categories
(Core :: Layout, defect)
Core
Layout
Tracking
()
RESOLVED
FIXED
mozilla52
Tracking | Status | |
---|---|---|
firefox52 | --- | fixed |
People
(Reporter: mstange, Unassigned)
References
Details
(Keywords: crash, regression)
Crash Data
[Tracking Requested - why for this release]:
This bug was filed from the Socorro interface and is
report bp-008460bb-7c3e-4044-8c7d-546f42161026.
=============================================================
This seems to have started with the Oct 25th Nightly.
https://crash-stats.mozilla.com/signature/?product=Firefox&signature=InvalidArrayIndex_CRASH%20%7C%20mozilla%3A%3AInactiveRefreshDriverTimer%3A%3ATickOne&date=%3E%3D2016-10-19T02%3A11%3A00.000Z&date=%3C2016-10-26T02%3A11%3A00.000Z&_columns=date&_columns=product&_columns=version&_columns=build_id&_columns=platform&_columns=reason&_columns=address&_sort=-date&page=1
Reporter | ||
Comment 1•8 years ago
|
||
This is a regression from bug 1198381.
Blocks: 1198381
Flags: needinfo?(afarre)
Reporter | ||
Comment 2•8 years ago
|
||
My guess is that you need to copy mNextDriverIndex into a local variable because it will change during the call to TickDriver.
Reporter | ||
Comment 3•8 years ago
|
||
Ah, bug 1198381 has already been backed out, so this will be fixed in the next nightly.
Status: NEW → RESOLVED
Closed: 8 years ago
tracking-firefox52:
? → ---
Flags: needinfo?(afarre)
Resolution: --- → FIXED
Target Milestone: --- → mozilla52
Comment 4•8 years ago
|
||
Good that we found it though, I'll make sure to include a fix for it.
Updated•8 years ago
|
Crash Signature: [@ InvalidArrayIndex_CRASH | mozilla::InactiveRefreshDriverTimer::TickOne] → [@ InvalidArrayIndex_CRASH | mozilla::InactiveRefreshDriverTimer::TickOne]
[@ InvalidArrayIndex_CRASH | nsTArray_Impl<T>::ElementAt | mozilla::InactiveRefreshDriverTimer::TickOne]
Comment 5•8 years ago
|
||
this was backed out so no longer affects 52
You need to log in
before you can comment on or make changes to this bug.
Description
•