Fix JSON parser Handle leak

Fix JSON parser Handle leak

R=verwaest@chromium.org
BUG=v8:3976
LOG=y

Committed: https://crrev.com/1ec850383bb82f6d8bebc7416e5f50b649d1eeaa
Cr-Commit-Position: refs/heads/master@{#27512}

[Erik Corry Chromium.org, 2015-03-27 13:40:32]

Rietveld isn't very good at indentation changes.  What's happened here is that
I've divided up the loop into two parts, one for when we are following
transitions and one for when we are not.  The one without the transitions is
fairly simple and has its own HandleScope so that we don't accumulate an
unlimited number of handles.  See
https://code.google.com/p/v8/issues/detail?id=3976#c10

[Erik Corry Chromium.org, 2015-03-27 13:59:38]

Performance numbers for Kraken look neutral.  There's a regression on
json-stringify-tinderbox on one platform, but that is supposed to be generating,
not parsing JSON.  Rerunning to see if it's a fluke.

[Erik Corry Chromium.org, 2015-03-27 14:15:34]

On 2015/03/27 13:59:38, Erik Corry Chromium.org wrote:
> Performance numbers for Kraken look neutral.  There's a regression on
> json-stringify-tinderbox on one platform, but that is supposed to be
generating,
> not parsing JSON.  Rerunning to see if it's a fluke.

It's not a fluke, but tinderbox really doesn't run this code, so I'm going to
put it down to unlucky GC timing.

64 bit: -0.45%
32 bit: +0.1%

[Toon Verwaest, 2015-03-30 08:34:31]

lgtm

[Erik Corry Chromium.org, 2015-03-30 08:37:39]

The CQ bit was checked by erikcorry@chromium.org

[commit-bot: I haz the power, 2015-03-30 08:37:44]

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

[commit-bot: I haz the power, 2015-03-30 08:54:32]

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

[commit-bot: I haz the power, 2015-03-30 08:54:33]

Try jobs failed on following builders:
  v8_win64_rel on tryserver.v8 (JOB_FAILED,
http://build.chromium.org/p/tryserver.v8/builders/v8_win64_rel/builds/3380)

[Erik Corry Chromium.org, 2015-03-30 09:00:20]

The CQ bit was checked by erikcorry@chromium.org

[commit-bot: I haz the power, 2015-03-30 09:00:32]

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

[commit-bot: I haz the power, 2015-03-30 09:14:24]

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

[commit-bot: I haz the power, 2015-03-30 09:14:25]

Try jobs failed on following builders:
  v8_win64_rel on tryserver.v8 (JOB_FAILED,
http://build.chromium.org/p/tryserver.v8/builders/v8_win64_rel/builds/3384)

[Erik Corry Chromium.org, 2015-03-30 09:31:52]

The CQ bit was checked by erikcorry@chromium.org

[Erik Corry Chromium.org, 2015-03-30 09:31:52]

The patchset sent to the CQ was uploaded after l-g-t-m from
verwaest@chromium.org
Link to the patchset: https://codereview.chromium.org/1041483004/#ps40001
(title: "Fix int width issue")

[commit-bot: I haz the power, 2015-03-30 09:32:03]

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

[commit-bot: I haz the power, 2015-03-30 09:55:22]

Committed patchset #3 (id:40001)

[commit-bot: I haz the power, 2015-03-30 09:55:42]

Patchset 3 (id:??) landed as
https://crrev.com/1ec850383bb82f6d8bebc7416e5f50b649d1eeaa
Cr-Commit-Position: refs/heads/master@{#27512}

[Erik Corry Chromium.org, 2015-04-01 09:22:27]

A revert of this CL (patchset #3 id:40001) has been created in
https://codereview.chromium.org/1052593002/ by erikcorry@chromium.org.

The reason for reverting is: Reverting due to JSOn parser failures.