Closed Bug 1503369 Opened 6 years ago Closed 6 years ago

Crash in SkTDArray<T>::swap

Categories

(Core :: XPCOM, defect)

Unspecified
Android
defect
Not set
critical

Tracking

()

RESOLVED WORKSFORME
Tracking Status
firefox63 --- wontfix
firefox64 --- fix-optional
firefox65 --- fix-optional

People

(Reporter: marcia, Unassigned)

Details

(Keywords: crash, regression)

Crash Data

This bug was filed from the Socorro interface and is report bp-3b532bf1-1310-423c-90d7-f56990181029. ============================================================= Seen while looking at nightly Android crash stats: https://bit.ly/2zd2tyN. Crashes started using 20180813100105 when nightly was still in 63 (but possibly earlier). Crashes seem to have happened only when nightly was in 63, 64 and now 65. Comments: *I was accessing the Netflix website *spotify web player Top 10 frames of crashing thread: 0 libxul.so SkTDArray<short>::swap gfx/skia/skia/include/core/SkTypes.h:306 1 libxul.so void nsPurpleBuffer::VisitEntries<SnowWhiteKiller> xpcom/base/nsCycleCollector.cpp:1143 2 libxul.so nsCycleCollector::FreeSnowWhiteWithBudget xpcom/base/nsCycleCollector.cpp:2980 3 libxul.so AsyncFreeSnowWhite::Run js/xpconnect/src/XPCJSRuntime.cpp:139 4 libxul.so IdleRunnableWrapper::Run xpcom/threads/nsThreadUtils.cpp:354 5 libxul.so nsThread::ProcessNextEvent xpcom/threads/nsThread.cpp:1245 6 libxul.so NS_ProcessNextEvent xpcom/threads/nsThreadUtils.cpp:530 7 libxul.so mozilla::ipc::MessagePump::Run ipc/glue/MessagePump.cpp:97 8 libxul.so MessageLoop::Run ipc/chromium/src/base/message_loop.cc:325 9 libxul.so nsBaseAppShell::Run widget/nsBaseAppShell.cpp:158 =============================================================
I think this is a signature morph of bug 1318810, and there is some corruption on the stack trace pointing to the skia code which is unlikely to be used on the garbage collector path.
Component: Graphics → XPCOM
There aren't any Firefox crashes with this signature in the last month so I'm closing this WFM. It seems likely the signature changed again or work in some other bug fixed the issue.
Status: NEW → RESOLVED
Closed: 6 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.