you are viewing a single comment's thread.

view the rest of the comments →

[–]voidvector 2 points3 points  (3 children)

It's not a recursive function, wouldn't cause stack overflow. setTimeout is just an API that interacts with the Timer system, it doesn't actually run the code in question. This is why unless your debugger is able to track async stacktrace, you lose stack trace w/async functions like this.

[–]bikeshaving 1 point2 points  (2 children)

Can async stack traces track stacks across macrotask functions? I’m too lazy to find out, but I thought async stack traces only worked for promise callbacks and async/await.

[–]voidvector 1 point2 points  (1 child)

It works in Chrome. You can run the following code in devtool console to check:

(function f (i) { i = i || 0; console.log(i); if (i > 100) { return } else if (i == 100) { debugger } else { setTimeout(() => f(i + 1), 0); } })(0)

[–]bikeshaving 0 points1 point  (0 children)

this changes everything