tools/memory_watcher/memory_hook.cc - Issue 43082: NO CODE CHANGE

Side by Side Diff

Use n/p to move between diff chunks; N/P to move between comments. Draft comments are only viewable by you.

Keyboard Shortcuts

	File
u :	up to issue
j / k :	jump to file after / before current file
J / K :	jump to next file with a comment after / before current file
	Side-by-side diff
i :	toggle intra-line diffs
e :	expand all comments
c :	collapse all comments
s :	toggle showing all comments
n / p :	next / previous diff chunk or comment
N / P :	next / previous comment
<Up> / <Down> :	next / previous line

	Issue
u :	up to list of issues
j / k :	jump to patch after / before current patch
o / <Enter> :	open current patch in side-by-side view
i :	open current patch in unified diff view

	Issue List
j / k :	jump to issue after / before current issue
o / <Enter> :	open current issue

Side by Side Diff: tools/memory_watcher/memory_hook.cc

Issue 43082: NO CODE CHANGE (Closed)

Patch Set: Created 11 years, 9 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:

« no previous file with comments | « tools/memory_watcher/memory_hook.h ('k') | tools/memory_watcher/memory_watcher.h » ('j') | no next file with comments »

OLD	NEW
1 // Copyright (c) 2006-2008 The Chromium Authors. All rights reserved.	1 // Copyright (c) 2006-2008 The Chromium Authors. All rights reserved.

2 // Use of this source code is governed by a BSD-style license that can be	2 // Use of this source code is governed by a BSD-style license that can be

3 // found in the LICENSE file.	3 // found in the LICENSE file.

4	4

5 // Static class for hooking Win32 API routines.	5 // Static class for hooking Win32 API routines.

6	6

7 // Some notes about how to hook Memory Allocation Routines in Windows.	7 // Some notes about how to hook Memory Allocation Routines in Windows.

8 //	8 //

9 // For our purposes we do not hook the libc routines. There are two	9 // For our purposes we do not hook the libc routines. There are two

10 // reasons for this. First, the libc routines all go through HeapAlloc	10 // reasons for this. First, the libc routines all go through HeapAlloc

(...skipping 535 matching lines...) Expand 10 before \| Expand all \| Expand 10 after Loading...
546 }	546 }

547	547

548 void MemoryHook::OnUntrack(HANDLE heap, int32 id, int32 size) {	548 void MemoryHook::OnUntrack(HANDLE heap, int32 id, int32 size) {

549 // Don't notify about allocations to our internal heap.	549 // Don't notify about allocations to our internal heap.

550 if (heap == heap_)	550 if (heap == heap_)

551 return;	551 return;

552	552

553 if (watcher_)	553 if (watcher_)

554 watcher_->OnUntrack(heap, id, size);	554 watcher_->OnUntrack(heap, id, size);

555 }	555 }

556

OLD	NEW