AuroraMiddleware/v8
1
0
Fork 0
Code Issues 2 Pull Requests Releases Wiki Activity
d8e8dab0e7
v8/test/inspector/debugger/set-async-call-stack-depth-expected.txt

38 lines
732 B
Plaintext
Raw Normal View History

[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: https://chromium.googlesource.com/v8/v8/+/1bca73bc832c645138bd3e0306fcaa8bb44dad04 Review-Url: https://codereview.chromium.org/2816043006 Cr-Commit-Position: refs/heads/master@{#44694}
2017-04-18 15:53:08 +00:00
Checks that we report not more then maxDepth call chains.
Running test: testPaused
[inspector] Add tests for Debugger domain New tests added for these calls: * evaluateOnCallFrame * setAsyncCallStackDepth * setBreakpoint * setVariableValue For setAsyncCallStackDepth, this change updates the test to manufacture async callstacks in a different way so that there is more than one. The previous promise chain method was broken by f61facf. Change-Id: I9083b0b1c08849d4c7ebb5349cfa4489f551aa39 Reviewed-on: https://chromium-review.googlesource.com/c/1465118 Commit-Queue: Jeff Fisher <jeffish@microsoft.com> Reviewed-by: Dmitry Gozman <dgozman@chromium.org> Cr-Commit-Position: refs/heads/master@{#59745}
2019-02-20 00:08:38 +00:00
Actual call chain length: 4
[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: https://chromium.googlesource.com/v8/v8/+/1bca73bc832c645138bd3e0306fcaa8bb44dad04 Review-Url: https://codereview.chromium.org/2816043006 Cr-Commit-Position: refs/heads/master@{#44694}
2017-04-18 15:53:08 +00:00
setAsyncCallStackDepth(maxDepth): 8
[inspector] Add tests for Debugger domain New tests added for these calls: * evaluateOnCallFrame * setAsyncCallStackDepth * setBreakpoint * setVariableValue For setAsyncCallStackDepth, this change updates the test to manufacture async callstacks in a different way so that there is more than one. The previous promise chain method was broken by f61facf. Change-Id: I9083b0b1c08849d4c7ebb5349cfa4489f551aa39 Reviewed-on: https://chromium-review.googlesource.com/c/1465118 Commit-Queue: Jeff Fisher <jeffish@microsoft.com> Reviewed-by: Dmitry Gozman <dgozman@chromium.org> Cr-Commit-Position: refs/heads/master@{#59745}
2019-02-20 00:08:38 +00:00
reported: 4
Actual call chain length: 4
setAsyncCallStackDepth(maxDepth): 4
reported: 4
[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: https://chromium.googlesource.com/v8/v8/+/1bca73bc832c645138bd3e0306fcaa8bb44dad04 Review-Url: https://codereview.chromium.org/2816043006 Cr-Commit-Position: refs/heads/master@{#44694}
2017-04-18 15:53:08 +00:00
[inspector] Add tests for Debugger domain New tests added for these calls: * evaluateOnCallFrame * setAsyncCallStackDepth * setBreakpoint * setVariableValue For setAsyncCallStackDepth, this change updates the test to manufacture async callstacks in a different way so that there is more than one. The previous promise chain method was broken by f61facf. Change-Id: I9083b0b1c08849d4c7ebb5349cfa4489f551aa39 Reviewed-on: https://chromium-review.googlesource.com/c/1465118 Commit-Queue: Jeff Fisher <jeffish@microsoft.com> Reviewed-by: Dmitry Gozman <dgozman@chromium.org> Cr-Commit-Position: refs/heads/master@{#59745}
2019-02-20 00:08:38 +00:00
Actual call chain length: 4
setAsyncCallStackDepth(maxDepth): 3
reported: 3
[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: https://chromium.googlesource.com/v8/v8/+/1bca73bc832c645138bd3e0306fcaa8bb44dad04 Review-Url: https://codereview.chromium.org/2816043006 Cr-Commit-Position: refs/heads/master@{#44694}
2017-04-18 15:53:08 +00:00
[inspector] Add tests for Debugger domain New tests added for these calls: * evaluateOnCallFrame * setAsyncCallStackDepth * setBreakpoint * setVariableValue For setAsyncCallStackDepth, this change updates the test to manufacture async callstacks in a different way so that there is more than one. The previous promise chain method was broken by f61facf. Change-Id: I9083b0b1c08849d4c7ebb5349cfa4489f551aa39 Reviewed-on: https://chromium-review.googlesource.com/c/1465118 Commit-Queue: Jeff Fisher <jeffish@microsoft.com> Reviewed-by: Dmitry Gozman <dgozman@chromium.org> Cr-Commit-Position: refs/heads/master@{#59745}
2019-02-20 00:08:38 +00:00
Actual call chain length: 4
[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: https://chromium.googlesource.com/v8/v8/+/1bca73bc832c645138bd3e0306fcaa8bb44dad04 Review-Url: https://codereview.chromium.org/2816043006 Cr-Commit-Position: refs/heads/master@{#44694}
2017-04-18 15:53:08 +00:00
setAsyncCallStackDepth(maxDepth): 0
reported: 0
Running test: testConsoleTrace
[inspector] Add tests for Debugger domain New tests added for these calls: * evaluateOnCallFrame * setAsyncCallStackDepth * setBreakpoint * setVariableValue For setAsyncCallStackDepth, this change updates the test to manufacture async callstacks in a different way so that there is more than one. The previous promise chain method was broken by f61facf. Change-Id: I9083b0b1c08849d4c7ebb5349cfa4489f551aa39 Reviewed-on: https://chromium-review.googlesource.com/c/1465118 Commit-Queue: Jeff Fisher <jeffish@microsoft.com> Reviewed-by: Dmitry Gozman <dgozman@chromium.org> Cr-Commit-Position: refs/heads/master@{#59745}
2019-02-20 00:08:38 +00:00
Actual call chain length: 4
[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: https://chromium.googlesource.com/v8/v8/+/1bca73bc832c645138bd3e0306fcaa8bb44dad04 Review-Url: https://codereview.chromium.org/2816043006 Cr-Commit-Position: refs/heads/master@{#44694}
2017-04-18 15:53:08 +00:00
setAsyncCallStackDepth(maxDepth): 8
[inspector] Add tests for Debugger domain New tests added for these calls: * evaluateOnCallFrame * setAsyncCallStackDepth * setBreakpoint * setVariableValue For setAsyncCallStackDepth, this change updates the test to manufacture async callstacks in a different way so that there is more than one. The previous promise chain method was broken by f61facf. Change-Id: I9083b0b1c08849d4c7ebb5349cfa4489f551aa39 Reviewed-on: https://chromium-review.googlesource.com/c/1465118 Commit-Queue: Jeff Fisher <jeffish@microsoft.com> Reviewed-by: Dmitry Gozman <dgozman@chromium.org> Cr-Commit-Position: refs/heads/master@{#59745}
2019-02-20 00:08:38 +00:00
reported: 4
Actual call chain length: 4
setAsyncCallStackDepth(maxDepth): 4
reported: 4
[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: https://chromium.googlesource.com/v8/v8/+/1bca73bc832c645138bd3e0306fcaa8bb44dad04 Review-Url: https://codereview.chromium.org/2816043006 Cr-Commit-Position: refs/heads/master@{#44694}
2017-04-18 15:53:08 +00:00
[inspector] Add tests for Debugger domain New tests added for these calls: * evaluateOnCallFrame * setAsyncCallStackDepth * setBreakpoint * setVariableValue For setAsyncCallStackDepth, this change updates the test to manufacture async callstacks in a different way so that there is more than one. The previous promise chain method was broken by f61facf. Change-Id: I9083b0b1c08849d4c7ebb5349cfa4489f551aa39 Reviewed-on: https://chromium-review.googlesource.com/c/1465118 Commit-Queue: Jeff Fisher <jeffish@microsoft.com> Reviewed-by: Dmitry Gozman <dgozman@chromium.org> Cr-Commit-Position: refs/heads/master@{#59745}
2019-02-20 00:08:38 +00:00
Actual call chain length: 4
setAsyncCallStackDepth(maxDepth): 3
reported: 3
[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: https://chromium.googlesource.com/v8/v8/+/1bca73bc832c645138bd3e0306fcaa8bb44dad04 Review-Url: https://codereview.chromium.org/2816043006 Cr-Commit-Position: refs/heads/master@{#44694}
2017-04-18 15:53:08 +00:00
[inspector] Add tests for Debugger domain New tests added for these calls: * evaluateOnCallFrame * setAsyncCallStackDepth * setBreakpoint * setVariableValue For setAsyncCallStackDepth, this change updates the test to manufacture async callstacks in a different way so that there is more than one. The previous promise chain method was broken by f61facf. Change-Id: I9083b0b1c08849d4c7ebb5349cfa4489f551aa39 Reviewed-on: https://chromium-review.googlesource.com/c/1465118 Commit-Queue: Jeff Fisher <jeffish@microsoft.com> Reviewed-by: Dmitry Gozman <dgozman@chromium.org> Cr-Commit-Position: refs/heads/master@{#59745}
2019-02-20 00:08:38 +00:00
Actual call chain length: 4
[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: https://chromium.googlesource.com/v8/v8/+/1bca73bc832c645138bd3e0306fcaa8bb44dad04 Review-Url: https://codereview.chromium.org/2816043006 Cr-Commit-Position: refs/heads/master@{#44694}
2017-04-18 15:53:08 +00:00
setAsyncCallStackDepth(maxDepth): 0
reported: 0
Reference in New Issue Copy Permalink