[tracing] Introduce MemoryDumpArgs to enable light and heavy dumps

base/trace_event/winheap_dump_provider_win.cc

 // Copyright 2015 The Chromium Authors. All rights reserved.
 // Use of this source code is governed by a BSD-style license that can be
 // found in the LICENSE file.
 
 #include "base/trace_event/winheap_dump_provider_win.h"
 
 #include <windows.h>
 
 #include "base/debug/profiler.h"
 #include "base/strings/string_util.h"
@@ skipping 29 matching lines @@
                         heap_info.block_count);
 }
 
 }  // namespace
 
 WinHeapDumpProvider* WinHeapDumpProvider::GetInstance() {
   return Singleton<WinHeapDumpProvider,
                    LeakySingletonTraits<WinHeapDumpProvider>>::get();
 }
 
-bool WinHeapDumpProvider::OnMemoryDump(ProcessMemoryDump* pmd) {
+bool WinHeapDumpProvider::OnMemoryDump(const MemoryDumpArgs& args,
+                                       ProcessMemoryDump* pmd) {
   // This method might be flaky for 2 reasons:
   //   - GetProcessHeaps is racy by design. It returns a snapshot of the
   //     available heaps, but there's no guarantee that that snapshot remains
   //     valid. If a heap disappears between GetProcessHeaps() and HeapWalk()
   //     then chaos should be assumed. This flakyness is acceptable for tracing.
   //   - The MSDN page for HeapLock says: "If the HeapLock function is called on
   //     a heap created with the HEAP_NO_SERIALIZATION flag, the results are
   //     undefined.". This is a problem on Windows XP where some system DLLs are
   //     known for creating heaps with this particular flag. For this reason
   //     this function should be disabled on XP.
@@ skipping 58 matching lines @@
     } else if ((heap_entry.wFlags & PROCESS_HEAP_REGION) != 0) {
       heap_info->committed_size += heap_entry.Region.dwCommittedSize;
     }
   }
   CHECK(::HeapUnlock(heap_info->heap_id) == TRUE);
   return true;
 }
 
 }  // namespace trace_event
 }  // namespace base