# debugger: Fix phantom JavaScript frames \(\#32469\) · gitcafe/zed

[View on GitCafe](https://git.cafe/gitcafe/zed/commit/295db79c47cf90f38597d6b6436a3c010b8226f9)

Repository: [gitcafe/zed](https://git.cafe/gitcafe/zed)

Visibility: public

Requested revision: 295db79c47cf90f38597d6b6436a3c010b8226f9

Requested commit: 295db79c47cf90f38597d6b6436a3c010b8226f9

Commit: 295db79c47cf90f38597d6b6436a3c010b8226f9

Tree: 19b037eca9ae41c67e5dfc9f0e2ea0469d8e888c

Author: Piotr Osiewicz

Committer: GitHub

## Message

```
debugger: Fix phantom JavaScript frames (#32469)

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>
```

## Parents

- [71d5c5711981e8ad53e3498471d22945fcc672dc](https://git.cafe/gitcafe/zed/commit/71d5c5711981e8ad53e3498471d22945fcc672dc?format=markdown)

[Source at this commit](https://git.cafe/gitcafe/zed/tree/295db79c47cf90f38597d6b6436a3c010b8226f9?format=markdown)