Don't create a handle scope when finalizing the bytecode

Don't create a handle scope when finalizing the bytecode

During finalization, we create SharedFunctionInfos which in turn
will create ScopeInfos for the Scopes in the AST. The Scopes then
cache a handle to the ScopeInfos. However, once the scope is closed,
all those handles get zapped, and it's no longer possible to access
the scopes (even though we actually still need the AST).

R=rmcilroy@chromium.org
BUG=

Committed: https://crrev.com/6c744a97151f4b55c0f401b397761a87030c8494
Cr-Commit-Position: refs/heads/master@{#38898}

[jochen (gone - plz use gerrit), 2016-08-25 10:54:52]

The CQ bit was checked by jochen@chromium.org to run a CQ dry run

[commit-bot: I haz the power, 2016-08-25 10:55:00]

Dry run: CQ is trying da patch. Follow status at
 
https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...

[rmcilroy, 2016-08-25 11:00:41]

This was to avoid a performance regression that introducing
CanonicalHandleScopes gave us, but didn't fully solve the regression anyway, so
I guess I'll have to find another solution.

LGTM.

[jochen (gone - plz use gerrit), 2016-08-25 11:02:18]

The CQ bit was unchecked by jochen@chromium.org

[jochen (gone - plz use gerrit), 2016-08-25 11:02:21]

The CQ bit was checked by jochen@chromium.org

[commit-bot: I haz the power, 2016-08-25 11:02:32]

CQ is trying da patch. Follow status at
 
https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...

[commit-bot: I haz the power, 2016-08-25 11:15:40]

Committed patchset #1 (id:1)

[commit-bot: I haz the power, 2016-08-25 11:16:05]

Description was changed from

==========
Don't create a handle scope when finalizing the bytecode

During finalization, we create SharedFunctionInfos which in turn
will create ScopeInfos for the Scopes in the AST. The Scopes then
cache a handle to the ScopeInfos. However, once the scope is closed,
all those handles get zapped, and it's no longer possible to access
the scopes (even though we actually still need the AST).

R=rmcilroy@chromium.org
BUG=
==========

to

==========
Don't create a handle scope when finalizing the bytecode

During finalization, we create SharedFunctionInfos which in turn
will create ScopeInfos for the Scopes in the AST. The Scopes then
cache a handle to the ScopeInfos. However, once the scope is closed,
all those handles get zapped, and it's no longer possible to access
the scopes (even though we actually still need the AST).

R=rmcilroy@chromium.org
BUG=

Committed: https://crrev.com/6c744a97151f4b55c0f401b397761a87030c8494
Cr-Commit-Position: refs/heads/master@{#38898}
==========

[commit-bot: I haz the power, 2016-08-25 11:16:06]

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