Make inaccurate GC stats reporting non-fatal in debug builds.

Not sure why this was fatal as it only hinders being able to report memory
issues to a debugging dev :P
This commit is contained in:
Moonchild 2024-09-21 15:38:34 +02:00 • committed by roytam1
commit efad094b02

View file

@ -2489,7 +2489,7 @@ ReportJSRuntimeExplicitTreeStats(const JS::RuntimeStats& rtStats,
// gcTotal is the sum of everything we've reported for the GC heap. It // gcTotal is the sum of everything we've reported for the GC heap. It
// should equal rtStats.gcHeapChunkTotal. // should equal rtStats.gcHeapChunkTotal.
MOZ_ASSERT(gcTotal == rtStats.gcHeapChunkTotal); NS_WARN_IF(gcTotal != rtStats.gcHeapChunkTotal);
} }
void void
@ -2929,7 +2929,7 @@ JSReporter::CollectReports(WindowPaths* windowPaths,
KIND_OTHER, rtStats.zTotals.regExpSharedsGCHeap, KIND_OTHER, rtStats.zTotals.regExpSharedsGCHeap,
"Used regexpshared cells."); "Used regexpshared cells.");
MOZ_ASSERT(gcThingTotal == rtStats.gcHeapGCThings); NS_WARN_IF(gcThingTotal == rtStats.gcHeapGCThings);
// Report xpconnect. // Report xpconnect.