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

Unified Diff: base/trace_event/memory_dump_manager.cc

Issue 1262333005: [tracing] Introduce MemoryDumpArgs to enable light and heavy dumps (Closed) Base URL: https://chromium.googlesource.com/chromium/src.git@master
Patch Set: Rebase. Created 5 years, 4 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: base/trace_event/memory_dump_manager.cc
diff --git a/base/trace_event/memory_dump_manager.cc b/base/trace_event/memory_dump_manager.cc
index d076dda05054ce70e2f5e009c7103d68ea03c6db..f9ba3ae5a134b23dcef8cfcb99a9e24a9e25fb44 100644
--- a/base/trace_event/memory_dump_manager.cc
+++ b/base/trace_event/memory_dump_manager.cc
@@ -311,8 +311,15 @@ void MemoryDumpManager::ContinueAsyncProcessDump(
// Invoke the dump provider without holding the |lock_|.
bool finalize = false;
bool dump_successful = false;
- if (!skip_dump)
- dump_successful = mdp->OnMemoryDump(&pmd_async_state->process_memory_dump);
+
+ // TODO(ssid): Change RequestGlobalDump to use MemoryDumpArgs along with
+ // MemoryDumpType to get request for light / heavy dump, and remove this
+ // constant.
+ if (!skip_dump) {
+ MemoryDumpArgs dump_args = {MemoryDumpArgs::LEVEL_OF_DETAIL_HIGH};
+ dump_successful =
+ mdp->OnMemoryDump(dump_args, &pmd_async_state->process_memory_dump);
+ }
{
AutoLock lock(lock_);
« no previous file with comments | « base/trace_event/memory_allocator_dump_unittest.cc ('k') | base/trace_event/memory_dump_manager_unittest.cc » ('j') | no next file with comments »

Powered by Google App Engine
This is Rietveld 408576698