1651841 - Code string run via setTimeout/Interval has no captured stack data

Status: NEW

(DevTools :: Debugger, defect, P3)

Description

[Logan Smyth [:loganfsmyth]]

Noticed while looking into https://bugzilla.mozilla.org/show_bug.cgi?id=1196089

Given these two functions:

1. setTimeout(() => { throw new Error(); }, 5);
2. setTimeout("throw new Error();", 5);

The first error will have a captured portion of the stack trace pointing to the callsite of setTimeout. The second will not have any captured stack data.

This is happening because passing a function uses the same DOM callback infrastructure used by everything else, whereas the second one is special parse + compile logic that does not capture any async frames.