This bug was filed from the Socorro interface and is report bp-059adc6b-60ea-40cf-a93d-1abc00170622. ============================================================= Crashing Thread (0) Frame Module Signature Source 0 xul.dll js::gc::GCRuntime::sweepAtomsTable(js::SliceBudget&) js/src/jsgc.cpp:5605 1 xul.dll js::gc::GCRuntime::sweepAtomsTable(js::gc::GCRuntime*, js::FreeOp*, JS::Zone*, js::SliceBudget&, js::gc::AllocKind) js/src/jsgc.cpp:5582 2 xul.dll js::gc::GCRuntime::performSweepActions(js::SliceBudget&, js::AutoLockForExclusiveAccess&) js/src/jsgc.cpp:5720 3 xul.dll js::gc::GCRuntime::incrementalCollectSlice(js::SliceBudget&, JS::gcreason::Reason, js::AutoLockForExclusiveAccess&) js/src/jsgc.cpp:6329 4 xul.dll js::gc::GCRuntime::gcCycle(bool, js::SliceBudget&, JS::gcreason::Reason) js/src/jsgc.cpp:6614 5 xul.dll js::gc::GCRuntime::collect(bool, js::SliceBudget, JS::gcreason::Reason) js/src/jsgc.cpp:6763 crash reports with this signature are newly showing up in firefox 55 - so far only from windows users. it looks related to bug 1369444.

Discussed during triage, ni on jcoppeard since he has been working in this area.

This is a continuation of the JSRuntime::sweepAtoms crashes (the code was moved into GCRuntime::sweepAtomsTable in bug 1369444). https://crash-stats.mozilla.com/signature/?signature=JSRuntime%3A%3AsweepAtoms&date=%3E%3D2017-01-06T11%3A57%3A23.000Z&date=%3C2017-07-06T11%3A57%3A23.000Z&_columns=date&_columns=product&_columns=version&_columns=build_id&_columns=platform&_columns=reason&_columns=address&_columns=install_time&_sort=-date&page=1#graphs This is probably heap corruption / bad memory.

(In reply to Jon Coppeard (:jonco) from comment #2) > This is a continuation of the JSRuntime::sweepAtoms crashes (the code was > moved into GCRuntime::sweepAtomsTable in bug 1369444). > > https://crash-stats.mozilla.com/signature/ > ?signature=JSRuntime%3A%3AsweepAtoms&date=%3E%3D2017-01-06T11%3A57%3A23. > 000Z&date=%3C2017-07-06T11%3A57%3A23. > 000Z&_columns=date&_columns=product&_columns=version&_columns=build_id&_colum > ns=platform&_columns=reason&_columns=address&_columns=install_time&_sort=- > date&page=1#graphs > > This is probably heap corruption / bad memory. Jon: From Triage team: Are there are any next steps here? Volume is not extremely high, but about 140 crashes in the last week.

I don't think there's anything we can usefully do here.

Not actionable as stated. Likely bad memory.