Bug 243668

Created attachment 461484 [details] testcase Please see the attached testcase. There is a series of async functions, c() calls b() calls a(), but if you open it on Safari, the stack shows: > throwError@async-error.html:4:18 > @async-error.html:8:13 > asyncFunctionResume@[native code] > @[native code] > promiseReactionJobWithoutPromise@[native code] > promiseReactionJob@[native code] which is not very useful. Firefox has a similar issue, but at least it doesn't show things from native code: > throwError@async-error.html:4:9 > a@async-error.html:8:3 Chrome has the best behavior that it can properly track across async frame: > Error > at throwError (async-error.html:4:9) > at a (async-error.html:8:3) > at async b (async-error.html:11:3) > at async c (async-error.html:14:3) Being able to track across async frame is important for knowing what is the right place to handle an error. Not being able to go across async frame means it is very hard to track the stack for any network errors.