Issue 226113006: Return 0 as maximal amount of physical memory if there is no limit.

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 226113006: Return 0 as maximal amount of physical memory if there is no limit. (Closed)

Created:
6 years, 8 months ago by jochen (gone - plz use gerrit)

Modified:
6 years, 8 months ago

Reviewers:
Michael Starzinger

CC:
v8-dev

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

Visibility:
Public.

Return 0 as maximal amount of physical memory if there is no limit. That's what the comment says should happen, and what Heap's ctor expects. BUG=none LOG=n R=mstarzinger@chromium.org Committed: https://code.google.com/p/v8/source/detail?r=20583

Created: 6 years, 8 months ago

Download [raw] [tar.bz2]

		Unified diffs	Side-by-side diffs	Delta from patch set	Stats (+1 line, -0 lines)			Patch
	M	src/platform-posix.cc	View		1 chunk	+1 line, -0 lines	0 comments	Download

Total messages: 3 (0 generated)

jochen (gone - plz use gerrit)

6 years, 8 months ago (2014-04-08 17:19:36 UTC) #3

Message was sent while issue was closed.

Committed patchset #1 manually as r20583 (presubmit successful).