Issue 391018: Fixed a few cases where allocators did not respect always_allocate,

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 391018: Fixed a few cases where allocators did not respect always_allocate, (Closed)

Created:
11 years, 1 month ago by Christian Plesner Hansen

Modified:
9 years, 7 months ago

Reviewers:
Mads Ager (chromium)

CC:
v8-dev

Visibility:
Public.

Description

Fixed a few cases where allocators did not respect always_allocate, potentially leading to bogus FatalProcessOutOfMemory situations. Also fixed a few cases where callers relied on getting a NewSpace object back (to avoid write barrier overhead) which they can't when always_allocate is in effect.

Patch Set 1 #

Created: 11 years, 1 month ago

Download [raw] [tar.bz2]

		Unified diffs	Side-by-side diffs	Delta from patch set	Stats (+12 lines, -10 lines)			Patch
	M	src/heap.cc	View		5 chunks	+11 lines, -6 lines	0 comments	Download
	M	src/runtime.cc	View		2 chunks	+1 line, -4 lines	0 comments	Download

Messages

Total messages: 2 (0 generated)

Expand Messages | Collapse Messages

Christian Plesner Hansen

This might fix http://code.google.com/p/chromium/issues/detail?id=17032.

11 years, 1 month ago (2009-11-11 15:16:29 UTC) #1

LGTM

Expand Messages | Collapse Messages