• kozyatinskiy's avatar
    [inspector] avoid cloning of async call chains · 1bca73bc
    kozyatinskiy authored
    - separated V8StackTraceImpl and AsyncStackTrace,
    - V8Debugger owns all AsyncStackTrace and cleanup half of them when limit is reached (first created - first cleaned),
    - V8StackTraceImpl, AsyncStackTrace and async-task-related tables in V8Debugger have weak reference to other async stack traces.
    - async tasks are cleared with related async stacks.
    
    BUG=v8:6189
    R=dgozman@chromium.org
    
    Review-Url: https://codereview.chromium.org/2816043006
    Cr-Commit-Position: refs/heads/master@{#44670}
    1bca73bc
Name
Last commit
Last update
..
benchmarks Loading commit data...
cctest Loading commit data...
common Loading commit data...
debugger Loading commit data...
fuzzer Loading commit data...
inspector Loading commit data...
intl Loading commit data...
js-perf-test Loading commit data...
memory Loading commit data...
message Loading commit data...
mjsunit Loading commit data...
mozilla Loading commit data...
preparser Loading commit data...
promises-aplus Loading commit data...
simdjs Loading commit data...
test262 Loading commit data...
unittests Loading commit data...
webkit Loading commit data...
BUILD.gn Loading commit data...
bot_default.gyp Loading commit data...
bot_default.isolate Loading commit data...
default.gyp Loading commit data...
default.isolate Loading commit data...
optimize_for_size.gyp Loading commit data...
optimize_for_size.isolate Loading commit data...
perf.gyp Loading commit data...
perf.isolate Loading commit data...