295db79c47
JavaScript debugger is using a phantom stack frame to delineate await points; that frame reuses a frame ID of 0, which collides with other frames returned from that adapter. https://github.com/microsoft/vscode-js-debug/blob/934075df8c3c9726ead99aa8ee6815b36d835c34/src/adapter/stackTrace.ts#L287 The bug has since been fixed in https://github.com/microsoft/vscode-js-debug/issues/2234, but we'll need to wait for a new release of node debugger for that to make a difference. Until then.. Release Notes: - Fixed a bug with JavaScript debugging which led to stack trace list containing excessive amount of `await` entries. --------- Co-authored-by: Conrad Irwin <conrad@zed.dev> Co-authored-by: Conrad Irwin <conrad.irwin@gmail.com>