Debugging v8.5 - always pauses in async_hooks.js on promise rejection

Have this code:

console.log('before');
Promise.reject(new Error('error'))

When I debug it in Chrome Devtools or VS Code, even when it's set to not break on exceptions, it pauses on function emitDestroyScript(asyncId) {... in async_hook.js after the promise is rejected.

The stack where it pauses is

emitDestroyScript (async_hooks.js:436)
_tickCallback (next_tick.js:175)
Module.runMain (module.js:667)
startup (bootstrap_node.js:201)
(anonymous function) (bootstrap_node.js:626)

The reason on the Debugger.paused message is "other".

Seeing the same issue

Same issue here while debuging with WebStorm 2017.2.4

@ak239

CC: @ak239

Same issue here while debuging with WebStorm 2017.2.4

@addaleax

cc @addaleax

This is driving me absolutely mental. Anyone got any ideas?

This also reproes in Node 8.6. Is anyone looking into this? Seems to be affecting quite a few people.

If anyone is dealing with this in VS Code, there is a workaround - add

"skipFiles": [
    "<node_internals>/**"
],

to your launch config to skip over this file automatically.

@roblourens

@roblourens After I added the "skipFiles" to config, it starts to pause on this line every time:

function rejected(value) { try { step(generator["throw"](value)); } catch (e) { reject(e); } }

and in Visual Studio current, not try fix

For me the quick fix works on Node 8.6 with latest VSCode on Ubuntu 17.04

Same issue here while debugging NodeJS 8.6 with WebStorm 2017.2.4 on MacOS 10.13

Yeah mine's the same.. still stopping on <node_internals> despite being correctly included in the skipFiles launch config

Month ago I was good with
"skipFiles": ["${workspaceFolder}/node_modules/**/*.js", "<node_internals>/**"]
But today I tried to step into await function and found myself in async_hooks.js...

I'm on vscode 1.47.3 and having this issue too. I can see that some have commented about this issue like 4/5 days ago so it must be something to do with recent updates? hmm

same issue...

I also started having this happen after a recent VS code update. I thought it had to do with the config of a new project I was working on, but I went back to one that worked a couple months ago and it is experiencing the same thing. I believe skipFiles no longer respects <node_internals>

Yes, I've had to manually skip all of those files (even though they're under <node_internals> which no longer works!) with this:

"skipFiles": [
              "<node_internals>", "node_modules", "loader.js", "async_hooks.js", "bootstrap.js", "**/async_hooks.js", "**/webpack/bootstrap", "**/internal/**/*", "**/domain.js", "**/events.js"
            ],

Very annoying but it works in the short term..

I can confirm this issue. <node_internals> is not working on skipFiles

For those that are landing on this page because skipFiles no longer works with node_internals, I can verify that these steps:
https://github.com/microsoft/vscode-js-debug#nightly-extension
fixes it. You're essentially switching to the nightly build of the debugger. Presumably this will only be necessary until they update the live debugger.

Yes, it was working with the skipFiles for very long, and suddenly it stoppped working.

I usually did this

            "skipFiles": [
                "${workspaceFolder}/node_modules/**/*.js",
                "<node_internals>/**/*.js"
              ]

I just tried it with the solution above and it can be solved with this too, at least for me it is enough

            "skipFiles": [
                "${workspaceFolder}/node_modules/**/*.js",
                "<node_internals>/**/*.js",
                "**/*async_hook*.js"
              ]

Following workaround worked for me.
Replace '<' and '>' with * (star) in the following,
"<node_internals>/**/*.js",

Looks like there is an issue with recognizing '<>' .
Give it a try.

How do you fix this without vsCode when running node via commandline?

Lol how is this still and issue when debugging with chrome?

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

"runtimeVersion": "14.9.0",

Apparently it is broken in Node v15

I'm using VS Code Insiders via Remote WSL, and I've tried every suggestion in this thread, including many combinations of skipFiles in my launch config as well as switching to the nightly build of the debugger, but I'm still having this issue. microsoft/vscode-js-debug#1085 (as mentioned in #36022) doesn't seem to have fixed it. I'm still brought into "internal\async_hooks" every time I debug. Aside from using an older version of Node (I'm on 16.x), is there a solution for this?

Was looking through the issue tracker for the thing fixed by #57148 because I figured I can't be the only one noticing it. I think people reporting after #16053 (which closed this issue) landed was probably seeing another issue coming from the unnecessary promise hooks unconditionally enabled through inspector async hooks. #57148 may fix at least some cases where the async hooks show up surprisingly.

Navigation Menu

Repository navigation

Debugging v8.5 - always pauses in async_hooks.js on promise rejection #15464

37 remaining items

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Debugging v8.5 - always pauses in async_hooks.js on promise rejection #15464

Description

Activity

TheAkio commented on Sep 19, 2017

kokeksibir commented on Sep 20, 2017

eugeneo commented on Sep 20, 2017

gunins commented on Sep 20, 2017

benjamingr commented on Sep 20, 2017

jpike88 commented on Sep 28, 2017

roblourens commented on Sep 28, 2017

Jeff-Li-Realster commented on Sep 29, 2017

nanshakov commented on Sep 29, 2017

TheAkio commented on Sep 29, 2017

maximilianschmid commented on Oct 2, 2017

37 remaining items

Leigh-M commented on Jul 23, 2020

DTX-92 commented on Jul 24, 2020

zaidrashid commented on Jul 28, 2020

Droppix commented on Jul 29, 2020

DillonSadofsky commented on Jul 30, 2020

Leigh-M commented on Jul 30, 2020

bernardolk commented on Jul 31, 2020

DillonSadofsky commented on Jul 31, 2020

katlimruiz commented on Aug 14, 2020

lokhandechetan commented on Aug 17, 2020

bendavis78 commented on Jan 10, 2021

quantuminformation commented on Apr 23, 2021

fabioespinosa commented on May 25, 2021

algotastic commented on Jun 29, 2022

joyeecheung commented on Feb 20, 2025

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions