377358516f
To improve performance, this patch makes Promise.all and Promise.race not perform correct catch prediction when the debugger is not open. The case may come up if Promise.race or Promise.all is called, then DevTools is open, then a component Promise is rejected. In this case, the user would falsely get an exception event even if the "pause on caught exceptions" box is unchecked. There are tests which triggered this case; however, it seems both unlikely and and acceptable to have an event in this case. Many analogous events are already produced when DevTools is enabled during the operation of a program. BUG=v8:3093 Review-Url: https://codereview.chromium.org/2350363002 Cr-Commit-Position: refs/heads/master@{#39565} |
||
---|---|---|
.. | ||
async-task-event.js | ||
evaluate-across-microtasks.js | ||
promise-all-caught.js | ||
promise-all-uncaught.js | ||
promise-race-caught.js | ||
promise-race-uncaught.js | ||
reentry.js | ||
reject-after-resolve.js | ||
reject-caught-all.js | ||
reject-caught-by-default-reject-handler.js | ||
reject-caught-late.js | ||
reject-caught-uncaught.js | ||
reject-in-constructor.js | ||
reject-uncaught-all.js | ||
reject-uncaught-late.js | ||
reject-uncaught-uncaught.js | ||
reject-with-invalid-reject.js | ||
reject-with-throw-in-reject.js | ||
reject-with-undefined-reject.js | ||
stepin-constructor.js | ||
stepin-handler.js | ||
throw-caught-all.js | ||
throw-caught-by-default-reject-handler.js | ||
throw-caught-late.js | ||
throw-caught-uncaught.js | ||
throw-eventually-caught.js | ||
throw-finally-caught-all.js | ||
throw-in-constructor.js | ||
throw-uncaught-all.js | ||
throw-uncaught-uncaught.js | ||
throw-with-throw-in-reject.js | ||
throw-with-undefined-reject.js | ||
try-reject-in-constructor.js | ||
try-throw-reject-in-constructor.js |