Issue 571913003: Use an upper bound for marking time estimation in idle notification.

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 571913003: Use an upper bound for marking time estimation in idle notification. (Closed)

Created:
6 years, 3 months ago by Hannes Payer (out of office)

Modified:
6 years, 3 months ago

Reviewers:
ulan

CC:
v8-dev

Base URL:
https://v8.googlecode.com/svn/branches/bleeding_edge

Project:
v8

Visibility:
Public.

Use an upper bound for marking time estimation in idle notification. BUG= R=ulan@chromium.org Committed: https://code.google.com/p/v8/source/detail?r=23954

Created: 6 years, 3 months ago

Download [raw] [tar.bz2]

		Unified diffs	Side-by-side diffs	Delta from patch set	Stats (+8 lines, -7 lines)			Patch
	M	src/heap/gc-idle-time-handler.cc	View		2 chunks	+5 lines, -4 lines	0 comments	Download
	M	src/heap/gc-idle-time-handler-unittest.cc	View		2 chunks	+3 lines, -3 lines	0 comments	Download

Total messages: 4 (1 generated)

Hannes Payer (out of office)

6 years, 3 months ago (2014-09-15 15:15:32 UTC) #4

Message was sent while issue was closed.

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