• jochen's avatar
    Don't create a handle scope when finalizing the bytecode · 6c744a97
    jochen authored
    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=
    
    Review-Url: https://codereview.chromium.org/2278933002
    Cr-Commit-Position: refs/heads/master@{#38898}
    6c744a97
Name
Last commit
Last update
benchmarks Loading commit data...
build_overrides Loading commit data...
docs Loading commit data...
gni Loading commit data...
gypfiles Loading commit data...
include Loading commit data...
infra Loading commit data...
samples Loading commit data...
src Loading commit data...
test Loading commit data...
testing Loading commit data...
third_party/binutils Loading commit data...
tools Loading commit data...
.clang-format Loading commit data...
.gitignore Loading commit data...
.gn Loading commit data...
.ycm_extra_conf.py Loading commit data...
AUTHORS Loading commit data...
BUILD.gn Loading commit data...
CODE_OF_CONDUCT.md Loading commit data...
ChangeLog Loading commit data...
DEPS Loading commit data...
LICENSE Loading commit data...
LICENSE.fdlibm Loading commit data...
LICENSE.strongtalk Loading commit data...
LICENSE.v8 Loading commit data...
LICENSE.valgrind Loading commit data...
Makefile Loading commit data...
Makefile.android Loading commit data...
OWNERS Loading commit data...
PRESUBMIT.py Loading commit data...
README.md Loading commit data...
WATCHLISTS Loading commit data...
codereview.settings Loading commit data...
snapshot_toolchain.gni Loading commit data...