This bug is for crash report bp-04a06fb1-bd02-4fd7-858a-d327f0190923. ``` Top 10 frames of crashing thread: 0 xul.dll js::AutoEnterOOMUnsafeRegion::crash js/src/vm/JSContext.cpp:1480 1 xul.dll js::AutoEnterOOMUnsafeRegion::crash js/src/vm/JSContext.cpp:1493 2 xul.dll js::TenuringTracer::traverse<JSObject> js/src/gc/Marking.cpp:2764 3 xul.dll class mozilla::Maybe<JS::Value> js::MapGCThingTyped<`lambda at z:/task_1568726031/build/src/js/src/gc/Marking.cpp:2780:43'> js/public/Value.h:1311 4 xul.dll js::gc::StoreBuffer::SlotsEdge::trace js/src/gc/Marking.cpp:2850 5 xul.dll js::gc::StoreBuffer::MonoTypeBuffer<js::gc::StoreBuffer::SlotsEdge>::trace js/src/gc/Marking.cpp:2799 6 xul.dll js::Nursery::doCollection js/src/gc/Nursery.cpp:932 7 xul.dll js::Nursery::collect js/src/gc/Nursery.cpp:839 8 xul.dll js::gc::GCRuntime::minorGC js/src/gc/GC.cpp:8085 9 xul.dll js::gc::GCRuntime::gcCycle js/src/gc/GC.cpp:7649 ``` these out-of-memory tab crash signatures in firefox spiked up across channels (release, beta) on september 24. there are no clear correlations, but looking at it in more detail it looks like the increase can mostly be tied to reports containing facebook.com as the crashing url. this table is a breakdown of how crash reports containing an url in the past couple of days: date | facebook | non-facebook | % facebook ----- | ---------- | ---------------- | ------------- 2019-09-18 | 36 | 46 | 43.9 2019-09-19 | 33 | 50 | 39.8 2019-09-20 | 42 | 61 | 40.8 2019-09-22 | 31 | 45 | 40.8 2019-09-23 | 39 | 51 | 43.3 2019-09-24 | 106 | 58 | 64.6 2019-09-25 | 141 | 59 | 70.5 2019-09-26 (not full day) | 84 | 32 | 72.4 maybe we can reach out to contacts at facebook to inquire if something changed in that particular time-frame that may have affected memory usage?
Bug 1584266 Comment 0 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
This bug is for crash report bp-04a06fb1-bd02-4fd7-858a-d327f0190923. ``` Top 10 frames of crashing thread: 0 xul.dll js::AutoEnterOOMUnsafeRegion::crash js/src/vm/JSContext.cpp:1480 1 xul.dll js::AutoEnterOOMUnsafeRegion::crash js/src/vm/JSContext.cpp:1493 2 xul.dll js::TenuringTracer::traverse<JSObject> js/src/gc/Marking.cpp:2764 3 xul.dll class mozilla::Maybe<JS::Value> js::MapGCThingTyped<`lambda at z:/task_1568726031/build/src/js/src/gc/Marking.cpp:2780:43'> js/public/Value.h:1311 4 xul.dll js::gc::StoreBuffer::SlotsEdge::trace js/src/gc/Marking.cpp:2850 5 xul.dll js::gc::StoreBuffer::MonoTypeBuffer<js::gc::StoreBuffer::SlotsEdge>::trace js/src/gc/Marking.cpp:2799 6 xul.dll js::Nursery::doCollection js/src/gc/Nursery.cpp:932 7 xul.dll js::Nursery::collect js/src/gc/Nursery.cpp:839 8 xul.dll js::gc::GCRuntime::minorGC js/src/gc/GC.cpp:8085 9 xul.dll js::gc::GCRuntime::gcCycle js/src/gc/GC.cpp:7649 ``` these out-of-memory tab crash signatures in firefox spiked up across channels (release, beta) on september 24. there are no clear correlations, but looking at it in more detail it looks like the increase can mostly be tied to reports containing facebook.com as the crashing url. this table is a breakdown of how crash reports containing an url have developed in the past couple of days: date | facebook | non-facebook | % facebook ----- | ---------- | ---------------- | ------------- 2019-09-18 | 36 | 46 | 43.9 2019-09-19 | 33 | 50 | 39.8 2019-09-20 | 42 | 61 | 40.8 2019-09-22 | 31 | 45 | 40.8 2019-09-23 | 39 | 51 | 43.3 2019-09-24 | 106 | 58 | 64.6 2019-09-25 | 141 | 59 | 70.5 2019-09-26 (not full day) | 84 | 32 | 72.4 maybe we can reach out to contacts at facebook to inquire if something changed in that particular time-frame that may have affected memory usage?
This bug is for crash report bp-04a06fb1-bd02-4fd7-858a-d327f0190923. ``` Top 10 frames of crashing thread: 0 xul.dll js::AutoEnterOOMUnsafeRegion::crash js/src/vm/JSContext.cpp:1480 1 xul.dll js::AutoEnterOOMUnsafeRegion::crash js/src/vm/JSContext.cpp:1493 2 xul.dll js::TenuringTracer::traverse<JSObject> js/src/gc/Marking.cpp:2764 3 xul.dll class mozilla::Maybe<JS::Value> js::MapGCThingTyped<`lambda at z:/task_1568726031/build/src/js/src/gc/Marking.cpp:2780:43'> js/public/Value.h:1311 4 xul.dll js::gc::StoreBuffer::SlotsEdge::trace js/src/gc/Marking.cpp:2850 5 xul.dll js::gc::StoreBuffer::MonoTypeBuffer<js::gc::StoreBuffer::SlotsEdge>::trace js/src/gc/Marking.cpp:2799 6 xul.dll js::Nursery::doCollection js/src/gc/Nursery.cpp:932 7 xul.dll js::Nursery::collect js/src/gc/Nursery.cpp:839 8 xul.dll js::gc::GCRuntime::minorGC js/src/gc/GC.cpp:8085 9 xul.dll js::gc::GCRuntime::gcCycle js/src/gc/GC.cpp:7649 ``` these out-of-memory tab crash signatures in firefox spiked up across channels (release, beta) on september 24. there are no clear correlations, but looking at it in more detail it looks like the increase can mostly be tied to reports containing facebook.com as the crashing url. this table is a breakdown of how crash reports containing an url have developed in the past couple of days: date | facebook | non-facebook | % facebook ----- | ---------- | ---------------- | ------------- 2019-09-18 | 36 | 46 | 43.9 2019-09-19 | 33 | 50 | 39.8 2019-09-20 | 42 | 61 | 40.8 2019-09-22 | 31 | 45 | 40.8 2019-09-23 | 39 | 51 | 43.3 2019-09-24 | 106 | 58 | 64.6 2019-09-25 | 141 | 59 | 70.5 2019-09-26 (not full day) | 84 | 32 | 72.4 maybe we can reach out to contacts at facebook to inquire if something changed in that particular time-frame that may have affected memory usage?
This bug is for crash report bp-04a06fb1-bd02-4fd7-858a-d327f0190923. ``` Top 10 frames of crashing thread: 0 xul.dll js::AutoEnterOOMUnsafeRegion::crash js/src/vm/JSContext.cpp:1480 1 xul.dll js::AutoEnterOOMUnsafeRegion::crash js/src/vm/JSContext.cpp:1493 2 xul.dll js::TenuringTracer::traverse<JSObject> js/src/gc/Marking.cpp:2764 3 xul.dll class mozilla::Maybe<JS::Value> js::MapGCThingTyped<`lambda at z:/task_1568726031/build/src/js/src/gc/Marking.cpp:2780:43'> js/public/Value.h:1311 4 xul.dll js::gc::StoreBuffer::SlotsEdge::trace js/src/gc/Marking.cpp:2850 5 xul.dll js::gc::StoreBuffer::MonoTypeBuffer<js::gc::StoreBuffer::SlotsEdge>::trace js/src/gc/Marking.cpp:2799 6 xul.dll js::Nursery::doCollection js/src/gc/Nursery.cpp:932 7 xul.dll js::Nursery::collect js/src/gc/Nursery.cpp:839 8 xul.dll js::gc::GCRuntime::minorGC js/src/gc/GC.cpp:8085 9 xul.dll js::gc::GCRuntime::gcCycle js/src/gc/GC.cpp:7649 ``` these out-of-memory tab crash signatures in firefox spiked up across channels (release, beta) on september 24. there are no clear correlations, but looking at it in more detail it looks like the increase can mostly be tied to reports containing facebook.com as the crashing url. this table is a breakdown of how crash reports containing an url have developed in the past couple of days: date | facebook | non-facebook | % facebook ----- | ---------- | ---------------- | ------------- 2019-09-18 | 36 | 46 | 43.9 2019-09-19 | 33 | 50 | 39.8 2019-09-20 | 42 | 61 | 40.8 2019-09-22 | 31 | 45 | 40.8 2019-09-23 | 39 | 51 | 43.3 2019-09-24 | 106 | 58 | 64.6 2019-09-25 | 141 | 59 | 70.5 2019-09-26 (not full day) | 84 | 32 | 72.4 maybe we can reach out to contacts at facebook to inquire if something changed in that particular time-frame that may have affected memory usage?