• 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
..
console Loading commit data...
cpu-profiler Loading commit data...
debugger Loading commit data...
heap-profiler Loading commit data...
runtime Loading commit data...
BUILD.gn Loading commit data...
DEPS Loading commit data...
OWNERS Loading commit data...
inspector-impl.cc Loading commit data...
inspector-impl.h Loading commit data...
inspector-test.cc Loading commit data...
inspector.gyp Loading commit data...
inspector.isolate Loading commit data...
inspector.status Loading commit data...
json-parse-expected.txt Loading commit data...
json-parse.js Loading commit data...
protocol-test.js Loading commit data...
task-runner.cc Loading commit data...
task-runner.h Loading commit data...
testcfg.py Loading commit data...