[heap] remove unneeded call to LowerInlineAllocationLimit

[heap] remove unneeded call to LowerInlineAllocationLimit

Calling LowerInlineAllocationLimit from the bottom of Heap::Scavenge seems to be
a no-op.

  new_space_.LowerInlineAllocationLimit(
      new_space_.inline_allocation_limit_step());

LowerInlineAllocatoinLimit does the following things:

1. Set the inline_allocation_limit_step_ to the passed in value. No-op.
2. Calls UpdateInlineAllocationLimit(0). This is unnecessary here as it has
   already been called when new_space_.ResetAllocationInfo was called above.
3. Sets top_on_previous_step_. This again is unnecessary as it gets reached by
   ResetAllocationInfo as well.

BUG=
R=hpayer@chromium.org,ulan@chromium.org

Committed: https://crrev.com/9f8e8b835a468b1622c5350a01a97bc32c5b2fb7
Cr-Commit-Position: refs/heads/master@{#31156}

[ofrobots, 2015-10-06 22:40:57]

The CQ bit was checked by ofrobots@google.com to run a CQ dry run

[commit-bot: I haz the power, 2015-10-06 22:41:08]

Dry run: CQ is trying da patch. Follow status at
 https://chromium-cq-status.appspot.com/patch-status/1390013002/1
View timeline at
 https://chromium-cq-status.appspot.com/patch-timeline/1390013002/1

[commit-bot: I haz the power, 2015-10-06 22:41:10]

The CQ bit was unchecked by commit-bot@chromium.org

[commit-bot: I haz the power, 2015-10-06 22:41:10]

Dry run: No L-G-T-M from a valid reviewer yet. Only full committers are
accepted.
Even if an L-G-T-M may have been provided, it was from a non-committer,
_not_ a full super star committer.
See http://www.chromium.org/getting-involved/become-a-committer
Note that this has nothing to do with OWNERS files.

[Hannes Payer (out of office), 2015-10-07 05:58:39]

lgtm

[ofrobots, 2015-10-07 14:55:17]

The CQ bit was checked by ofrobots@google.com

[commit-bot: I haz the power, 2015-10-07 14:55:38]

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

[commit-bot: I haz the power, 2015-10-07 15:19:44]

Committed patchset #2 (id:20001)

[commit-bot: I haz the power, 2015-10-07 15:20:06]

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

[ofrobots, 2015-10-25 10:18:27]

A revert of this CL (patchset #2 id:20001) has been created in
https://codereview.chromium.org/1405043005/ by ofrobots@google.com.

The reason for reverting is: Causes memory footprint regression:
https://code.google.com/p/chromium/issues/detail?id=541135

The intent of the code here was to advance the inline allocation limit without
counting the allocated memory towards a step. Calling LowerInlineAllocationLimit
this way is a blunt way of doing it, but it works.

At this point it is simplest to revert this CL. My follow-on CL
(https://codereview.chromium.org/1404523002/) can address the 'bluntness' of
calling LowerInlineAllocationLimit from here along with leaving a comment about
the intent.

revert_cq: 1
revert_reason_textarea: Causes memory footprint regression:
https://code.google.com/p/chromium/issues/detail?id=541135

The intent of the code here was to advance the inline allocation limit without
counting the allocated memory towards a step. Calling LowerInlineAllocationLimit
this way is a blunt way of doing it, but it works.

At this point it is simplest to revert this CL. My follow-on CL
(https://codereview.chromium.org/1404523002/) can address the 'bluntness' of
calling LowerInlineAllocationLimit from here along with leaving a comment about
the intent..