`async_hooks` is raised on Step in debugging into `async`/`await` function and on leaving `await` function

[pubmikeb]

• Version: v16.0.0-nightly2020110785b42af439
• Platform: Windows 10 x64 20H2

What steps will reproduce the bug?

I've paid attention that now when I click on Step Into on async/await function debugger goes to the Node.js internal async_hooks file instead of jumping to the wanted async/await function (screencast: Video_2020-11-07_123421.zip).

How often does it reproduce? Is there a required condition?

Currently the debugging experience of async/await functions is much more problematic, I always have to firstly go away from async_hooks to reach the wanted function, which I actually need to debug. The same things happens when I leave the async/await function, I'm firstly forwarded to async_hooks and only then to the initial function, where I've started my debugging.

What is the expected behavior?

When I click on Step Into, I expect to be forwarded to the function itself, not to the async_hooks.

What do you see instead?

I always have to firstly go away from async_hooks to reach the wanted function, which I actually need to debug.

Additional information

I've assumed it is an issue of the IDEA/WebStorm, but the JetBrains Team confirms such behavior on VSCode as well.
Please check if it is a regression.

Sample IDEA/WebStrom project (WEB-48157.zip). Please, put the breakpoint on the line #23 (app.js) and try to debug the await tst("Boo"); function. Are you also redirected to async_hooks firstly?

[Jamesernator]

Stepping in all scripts is just how v8's debugger works, it sounds like you can tell IDEA to skip stepping into some files: https://www.jetbrains.com/help/idea/settings-debugger-stepping.html#aa57f

[pubmikeb]

The key thing is that I started to observe such behavior just since v16.0.0-nightly2020110785b42af439, previously I've never landed to async_hooks during the debugging (at function entrance and upon the leaving the function). That's why I've raised a ticket.

[connor4312]

I received a report of this in the VS Code debugger and reproduced on 15.8.0 (microsoft/vscode#115670). Although we set blackbox patterns for files including ^node:internal\/async_hooks$, the debugger pauses there regardless

Here's a complete log file: https://memes.peet.io/img/vscode-debugadapter-f1a21bb1.json.gz. You can open it in our tool and enter async_hooks on the grep box on the right side to see the relevant traffic to and from the debugger.

[arciisine]

I've just run into this issue as well, and no amount of configuration seems to affect it. I've seen #15464, which seems to indicate a similar problem was fixed. This seems to have been a regression somwhere in the 15.x line.

[bodqhrohro]

I experience the same on v12.19.0 in Chromium debugger. And even stepping out of async_hooks does not help: the execution continues to the caller, skipping the awaited function entirely. And if I keep piling through lots of internal functions, I just get lost and have to go through lots of other hooks not related to the inspected one, but have a chance to finally run into it if being patient and observant enough.

[fabioespinosa]

For those struggling with the VS code debugger, this config helped (along with the skipFiles):

"runtimeVersion": "14.9.0",

[breautek]

I experience the same on v12.19.0 in Chromium debugger. And even stepping out of async_hooks does not help: the execution continues to the caller, skipping the awaited function entirely. And if I keep piling through lots of internal functions, I just get lost and have to go through lots of other hooks not related to the inspected one, but have a chance to finally run into it if being patient and observant enough.

Encountered the same experiences on v12.22.1 and also tested the latest v.16.4.0 release. I believe it only occurs on functions using the async / await keywords. I've migrated a lot of code to use this for readability over the last year but now I need to actually debug a complicated problem where using the inspector is necessary, and it's nearly impossible to walk through the code. I basically can't use step into and instead have to manually go to the function to add a breakpoint so that I can "Continue" to the breakpoint instead of using the Step commands so that I can skip over internal/async_hooks. Incredibly tedious...

[jackhollowaypersonal]

Is there still no workaround for this? I cannot use 14.9.0 without Rosetta as I'm on Apple Silicon.

[pubmikeb]

The problem (WEB-48157) has been fixed for IntelliJ IDEA starting 2021.2 EAP (212.4535.15 build).

[jackhollowaypersonal]

The problem (WEB-48157) has been fixed for IntelliJ IDEA starting 2021.2 EAP (212.4535.15 build).

Just waiting on VSCode fix now then I take it?

[breautek]

The problem (WEB-48157) has been fixed for IntelliJ IDEA starting 2021.2 EAP (212.4535.15 build).

I wouldn't really call this a fix, just a workaround being implemented by that editor.

Based this thread this issue occurs with:

• IntelliJ (with a workaround being implemented in an upcoming release)
• VSCode
• Google Chrome DevTools

Based on previous comment:

Stepping in all scripts is just how v8's debugger works

It sounds like the real issue is with Node's decision of using these internal JS code being injected/used.

Related: #11893