Honour PartitionAllocReturnNull flag when MEMORY_TOOL_REPLACES_ALLOCATOR

Honour PartitionAllocReturnNull flag when MEMORY_TOOL_REPLACES_ALLOCATOR

Previously, for builds defining MEMORY_TOOL_REPLACES_ALLOCATOR, the
PartitionAllocReturnNull flag was not respected. This can causes problems on
cluster-fuzz, due to generating valid scripts which ought to just throw a
RangeError (as they do in ordinary builds) rather than crashing.

BUG=617628
R=jochen@chromium.org, littledan@chromium.org

Committed: https://crrev.com/7757f92ee97b2668c3f412fa0ebdb62321d8bd0d
Cr-Commit-Position: refs/heads/master@{#398422}

[caitp (gmail), 2016-06-07 12:05:50]

Please take a quick look

[caitp (gmail), 2016-06-07 12:06:21]

Description was changed from

==========
Honour PartitionAllocReturnNull flag when MEMORY_TOOL_REPLACES_ALLOCATOR

Previously, for builds defining MEMORY_TOOL_REPLACES_ALLOCATOR, the
PartitionAllocReturnNull flag was not respected. This can causes problems on
cluster-fuzz, due to generating valid scripts which ought to just throw a
RangeError rather than crashing (as they do in ordinary builds).

BUG=617628
R=jochen@chromium.org, littledan@chromium.org
==========

to

==========
Honour PartitionAllocReturnNull flag when MEMORY_TOOL_REPLACES_ALLOCATOR

Previously, for builds defining MEMORY_TOOL_REPLACES_ALLOCATOR, the
PartitionAllocReturnNull flag was not respected. This can causes problems on
cluster-fuzz, due to generating valid scripts which ought to just throw a
RangeError (as they do in ordinary builds) rather than crashing.

BUG=617628
R=jochen@chromium.org, littledan@chromium.org
==========

[Dan Ehrenberg, 2016-06-07 13:51:52]

lgtm

Seems good to me, but someone with more experience in this code should also
review.

[caitp (gmail), 2016-06-07 15:59:35]

On 2016/06/07 13:51:52, Dan Ehrenberg wrote:
> lgtm
> 
> Seems good to me, but someone with more experience in this code should also
> review.

jochen is a Source/wtf owner, but I'll add some other names

[caitp (gmail), 2016-06-07 16:04:36]

caitpotter88@gmail.com changed reviewers:
+ bashi@chromium.org, haraken@chromium.org

[caitp (gmail), 2016-06-07 16:05:32]

caitpotter88@gmail.com changed reviewers:
- bashi@chromium.org

[jochen (gone - plz use gerrit), 2016-06-07 18:48:58]

lgtm

[caitp (gmail), 2016-06-07 19:07:19]

The CQ bit was checked by caitpotter88@gmail.com

[commit-bot: I haz the power, 2016-06-07 19:07:36]

CQ is trying da patch. Follow status at
 https://chromium-cq-status.appspot.com/patch-status/2044673003/20001

[haraken, 2016-06-07 23:37:06]

LGTM

[commit-bot: I haz the power, 2016-06-07 23:59:04]

Description was changed from

==========
Honour PartitionAllocReturnNull flag when MEMORY_TOOL_REPLACES_ALLOCATOR

Previously, for builds defining MEMORY_TOOL_REPLACES_ALLOCATOR, the
PartitionAllocReturnNull flag was not respected. This can causes problems on
cluster-fuzz, due to generating valid scripts which ought to just throw a
RangeError (as they do in ordinary builds) rather than crashing.

BUG=617628
R=jochen@chromium.org, littledan@chromium.org
==========

to

==========
Honour PartitionAllocReturnNull flag when MEMORY_TOOL_REPLACES_ALLOCATOR

Previously, for builds defining MEMORY_TOOL_REPLACES_ALLOCATOR, the
PartitionAllocReturnNull flag was not respected. This can causes problems on
cluster-fuzz, due to generating valid scripts which ought to just throw a
RangeError (as they do in ordinary builds) rather than crashing.

BUG=617628
R=jochen@chromium.org, littledan@chromium.org
==========

[commit-bot: I haz the power, 2016-06-07 23:59:04]

Committed patchset #2 (id:20001)

[commit-bot: I haz the power, 2016-06-08 00:00:45]

Description was changed from

==========
Honour PartitionAllocReturnNull flag when MEMORY_TOOL_REPLACES_ALLOCATOR

Previously, for builds defining MEMORY_TOOL_REPLACES_ALLOCATOR, the
PartitionAllocReturnNull flag was not respected. This can causes problems on
cluster-fuzz, due to generating valid scripts which ought to just throw a
RangeError (as they do in ordinary builds) rather than crashing.

BUG=617628
R=jochen@chromium.org, littledan@chromium.org
==========

to

==========
Honour PartitionAllocReturnNull flag when MEMORY_TOOL_REPLACES_ALLOCATOR

Previously, for builds defining MEMORY_TOOL_REPLACES_ALLOCATOR, the
PartitionAllocReturnNull flag was not respected. This can causes problems on
cluster-fuzz, due to generating valid scripts which ought to just throw a
RangeError (as they do in ordinary builds) rather than crashing.

BUG=617628
R=jochen@chromium.org, littledan@chromium.org

Committed: https://crrev.com/7757f92ee97b2668c3f412fa0ebdb62321d8bd0d
Cr-Commit-Position: refs/heads/master@{#398422}
==========

[commit-bot: I haz the power, 2016-06-08 00:00:46]

Patchset 2 (id:??) landed as
https://crrev.com/7757f92ee97b2668c3f412fa0ebdb62321d8bd0d
Cr-Commit-Position: refs/heads/master@{#398422}