Chromium Code Reviews| Index: base/trace_event/winheap_dump_provider_win.cc |
| diff --git a/base/trace_event/winheap_dump_provider_win.cc b/base/trace_event/winheap_dump_provider_win.cc |
| index 7d003c96979a9dae53bef4479bd3ba6bdc129763..80956369cca218a4247a1e36fe873ca9da963670 100644 |
| --- a/base/trace_event/winheap_dump_provider_win.cc |
| +++ b/base/trace_event/winheap_dump_provider_win.cc |
| @@ -80,7 +80,7 @@ bool WinHeapDumpProvider::OnMemoryDump(const MemoryDumpArgs& args, |
| // |
| // This is inherently racy as is, but it's not something that we observe a lot |
| // in Chrome, the heaps tend to be created at startup only. |
| - scoped_ptr<HANDLE[]> all_heaps(new HANDLE[number_of_heaps]); |
| + std::unique_ptr<HANDLE[]> all_heaps(new HANDLE[number_of_heaps]); |
| if (::GetProcessHeaps(number_of_heaps, all_heaps.get()) != number_of_heaps) |
|
Nico
2016/04/04 17:14:56
(i was wondering if this leaks the contents of all
|
| return false; |