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

V8/C++ error with [email protected] #13

Closed
TehShrike opened this issue Jun 27, 2017 · 4 comments
Closed

V8/C++ error with [email protected] #13

TehShrike opened this issue Jun 27, 2017 · 4 comments

Comments

@TehShrike
Copy link
Member

Sorry for the incomplete reproduction - here's what I know so far:

When I build https://github.com/tehshrike/revelation-timeline with [email protected], on node 7 or 8 (I haven't tested on 6 or older), node crashes with this stack trace:

/usr/local/bin/node[4247]: ../src/node_file.cc:527:void node::InternalModuleReadFile(const FunctionCallbackInfo<v8::Value> &): Assertion `(numchars) >= (0)' failed.
 1: node::Abort() [/usr/local/bin/node]
 2: node::MakeCallback(v8::Isolate*, v8::Local<v8::Object>, char const*, int, v8::Local<v8::Value>*, double, double) [/usr/local/bin/node]
 3: node::InternalModuleReadFile(v8::FunctionCallbackInfo<v8::Value> const&) [/usr/local/bin/node]
 4: 0x2ae4aa8e9a65
sh: line 1:  4242 Abort trap: 6

I suspect it is related to this node.js issue, and after this pull request is merged, there would be a much more useful stack trace.

Rolling back to the latest version of [email protected] eliminates the crash.

@Rich-Harris
Copy link
Member

Amazingly, if you click the link to [email protected], your computer will try and send the plugin an email.

Anyway: I don't know if this fixes anything but it's at least possible — I've released 2.0.3 which bails as soon as it sees a module ID that begins with \0 (since that indicates that a module was generated by a plugin and therefore isn't relevant). Will leave this open in case it's not fixed.

@nikolaswise
Copy link

I had this trub myself; updating to the 2.0.3 patch seems to have cleared it up.

@TehShrike
Copy link
Member Author

The revelation-timeline project is in a bit of upheaval at the moment, but I did go back and try building with 2.0.3 and didn't see any errors.

@TehShrike
Copy link
Member Author

everything is cool and life is good 👍

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