Bug 806239 - When we dump memory reports after minimizing memory usage, we shouldn't also dump the reports before minimizing. r=njn, a=bajaj
authorJustin Lebar <justin.lebar@gmail.com>
Sun, 28 Oct 2012 20:18:40 -0400
changeset 113774 df7645bd936c9ea4cde0eb625521f46731c4c1c0
parent 113773 1ea0c1cf9d2a3821ff83ec62e67259372ddcd24a
child 113775 eb1ad7ebda1802bad90b147906fee286993f3235
push idunknown
push userunknown
push dateunknown
reviewersnjn, bajaj
bugs806239
milestone18.0a2
Bug 806239 - When we dump memory reports after minimizing memory usage, we shouldn't also dump the reports before minimizing. r=njn, a=bajaj
xpcom/base/MemoryInfoDumper.cpp
--- a/xpcom/base/MemoryInfoDumper.cpp
+++ b/xpcom/base/MemoryInfoDumper.cpp
@@ -319,16 +319,17 @@ MemoryInfoDumper::DumpMemoryReportsToFil
     nsRefPtr<DumpMemoryReportsRunnable> callback =
       new DumpMemoryReportsRunnable(identifier,
           /* minimizeMemoryUsage = */ false,
           /* dumpChildProcesses = */ false);
     nsCOMPtr<nsIMemoryReporterManager> mgr =
       do_GetService("@mozilla.org/memory-reporter-manager;1");
     NS_ENSURE_TRUE(mgr,);
     mgr->MinimizeMemoryUsage(callback);
+    return;
   }
 
   DumpMemoryReportsToFileImpl(identifier);
 }
 
 /* static */ void
 MemoryInfoDumper::DumpGCAndCCLogsToFile(
   const nsAString& aIdentifier,