v8/test/inspector/debugger/set-async-call-stack-depth-expected.txt
kozyatinskiy 38be4a17c1 [inspector] avoid cloning of async call chains
- 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-Original-Commit-Position: refs/heads/master@{#44670}
Committed: 1bca73bc83
Review-Url: https://codereview.chromium.org/2816043006
Cr-Commit-Position: refs/heads/master@{#44694}
2017-04-18 15:53:08 +00:00

38 lines
734 B
Plaintext

Checks that we report not more then maxDepth call chains.
Running test: testPaused
Actual call chain length: 8
setAsyncCallStackDepth(maxDepth): 16
reported: 8
Actual call chain length: 8
setAsyncCallStackDepth(maxDepth): 8
reported: 8
Actual call chain length: 8
setAsyncCallStackDepth(maxDepth): 7
reported: 7
Actual call chain length: 8
setAsyncCallStackDepth(maxDepth): 0
reported: 0
Running test: testConsoleTrace
Actual call chain length: 8
setAsyncCallStackDepth(maxDepth): 16
reported: 8
Actual call chain length: 8
setAsyncCallStackDepth(maxDepth): 8
reported: 8
Actual call chain length: 8
setAsyncCallStackDepth(maxDepth): 7
reported: 7
Actual call chain length: 8
setAsyncCallStackDepth(maxDepth): 0
reported: 0