Chromium Code Reviews
chromiumcodereview-hr@appspot.gserviceaccount.com (chromiumcodereview-hr) | Please choose your nickname with Settings | Help | Chromium Project | Gerrit Changes | Sign out
(579)

Unified Diff: content/browser/browser_main_loop.cc

Issue 1333873002: [tracing] Fix MemoryDumpManager to support startup tracing (Closed) Base URL: https://chromium.googlesource.com/chromium/src.git@master
Patch Set: Re dsinclair #5 (nits, invert Initialize args) Created 5 years, 3 months ago
Use n/p to move between diff chunks; N/P to move between comments. Draft comments are only viewable by you.
Jump to:
View side-by-side diff with in-line comments
Download patch
Index: content/browser/browser_main_loop.cc
diff --git a/content/browser/browser_main_loop.cc b/content/browser/browser_main_loop.cc
index b8c41e07d78768d46e1345a38ca6159176504d14..eb294ef5a467233e7c7a391b7c9edccfed75375b 100644
--- a/content/browser/browser_main_loop.cc
+++ b/content/browser/browser_main_loop.cc
@@ -642,9 +642,7 @@ void BrowserMainLoop::PostMainMessageLoopStart() {
DOMStorageArea::EnableAggressiveCommitDelay();
}
- base::trace_event::MemoryDumpManager::GetInstance()->Initialize();
-
- // Enable the dump providers.
+ // Enable memory-infra dump providers.
base::trace_event::MemoryDumpManager::GetInstance()->RegisterDumpProvider(
HostSharedBitmapManager::current());
base::trace_event::MemoryDumpManager::GetInstance()->RegisterDumpProvider(
« no previous file with comments | « components/tracing/child_memory_dump_manager_delegate_impl.cc ('k') | content/browser/tracing/memory_tracing_browsertest.cc » ('j') | no next file with comments »

Powered by Google App Engine
This is Rietveld 408576698