Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Getting "node::AsyncWrap::AsyncWrap init hook threw" error when using 2.0.2 #21

Closed
saintedlama opened this issue Jan 12, 2016 · 5 comments

Comments

@saintedlama
Copy link

maintainer edit: If you are experiencing this issue, please file a new issue. This is a common error message and can be caused by many different things.

After updating to 2.0.2 (from 2.0.1) I'm getting a FATAL ERROR: node::AsyncWrap::AsyncWrap init hook threw error when using trace.

Tested with node.js versions 4.2.3 and 4.2.4 on windows

@AndreasMadsen
Copy link
Owner

The tests parse, so I will need a testcase to debug this.

@AndreasMadsen
Copy link
Owner

Node 4.2.5 have been released. This is compatible with latest version of trace (2.2.1), this should solve any issues.

@aleung
Copy link

aleung commented Mar 1, 2016

@AndreasMadsen Which node.js 5.x version is compatible with trace 2.3.0? I'm using node 5.3.0 have the same issue.

@AndreasMadsen
Copy link
Owner

AndreasMadsen commented Mar 1, 2016

@aleung 2.3.0 is definitely compatible with 5.7.0

I tested on node 5.3.0 and it appears that npm installs async-hook@1.3.0 (works with 5.7.0) as a trace dependency, where is should install async-hook@1.2.0 (works with 5.3.0 to 5.6.x). The engine field is correctly specified, npm just don't use it for version selection.

The best I can suggests, is that you manually replace the async-hook with async-hook@1.2.0. If you have any better ideas please let me know.

Your issue has very little todo with this issue. The error is very common when using async-wrap / async-hook,. But I understand the confusing. I've edited the first comment to notify others.

@AndreasMadsen
Copy link
Owner

AndreasMadsen commented Apr 17, 2016

Tracking issue: nodejs/Release#86

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants