Issue 1211633002: Introduce mechanism to record an allocation of a class

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

Issue 1211633002: Introduce mechanism to record an allocation of a class (Closed)

Created:
5 years, 6 months ago by Cutch

Modified:
5 years, 6 months ago

Reviewers:
rmacnak

CC:
reviews_dartlang.org, vm-dev_dartlang.org

Base URL:
git@github.com:dart-lang/sdk.git@master

Target Ref:
refs/heads/master

Visibility:
Public.

Introduce mechanism to record an allocation of a class - Use a bit in RawClass to remember if we are tracing allocation for this class. - Add Profiler::RecordAllocation - Add a simple heartbeat test for Profiler::RecordAllocation R=rmacnak@google.com Committed: https://github.com/dart-lang/sdk/commit/26b5b2e95ba56429464bfd033e10753dbc4119de

Created: 5 years, 6 months ago

Download [raw] [tar.bz2]

	Unified diffs	Side-by-side diffs	Stats (+116 lines, -2 lines)			Patch
M	runtime/vm/object.h	View	3 chunks	+7 lines, -0 lines	0 comments	Download
M	runtime/vm/object.cc	View	3 chunks	+18 lines, -2 lines	0 comments	Download
M	runtime/vm/profiler.h	View	2 chunks	+7 lines, -0 lines	0 comments	Download
M	runtime/vm/profiler.cc	View	1 chunk	+52 lines, -0 lines	0 comments	Download
M	runtime/vm/profiler_test.cc	View	1 chunk	+32 lines, -0 lines	0 comments	Download

Total messages: 4 (1 generated)

Cutch

5 years, 6 months ago (2015-06-24 20:41:18 UTC) #4

Message was sent while issue was closed.

Committed patchset #1 (id:1) manually as
26b5b2e95ba56429464bfd033e10753dbc4119de (presubmit successful).