Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Looks like a serious v8 bug

See original GitHub issue

I’m using NW.js 0.21.6 SDK, although I upgraded from 0.21.4. I was running tests just compiling a Jade file through Accord (https://github.com/jescalan/accord).

However, this error doesn’t look like anything related to a JS error, is that correct? I’m wondering if this is just an error with Chromium 57 related to NW.js. Output follows:

FATAL ERROR: v8::Context::SetAlignedPointerInEmbedderData() Pointer is not aligned
 1: node::Abort() [/usr/local/lib/node_modules/nw/nwjs/nwjs.app/Contents/Versions/57.0.2987.133/nwjs Framework.framework/libnode.dylib]
 2: node::FatalException(v8::Isolate*, v8::Local<v8::Value>, v8::Local<v8::Message>) [/usr/local/lib/node_modules/nw/nwjs/nwjs.app/Contents/Versions/57.0.2987.133/nwjs Framework.framework/libnode.dylib]
 3: v8::Context::SetAlignedPointerInEmbedderData(int, void*) [/usr/local/lib/node_modules/nw/nwjs/nwjs.app/Contents/Versions/57.0.2987.133/nwjs Framework.framework/nwjs Framework]
 4: node::ContextifyContext::CreateV8Context(node::Environment*, v8::Local<v8::Object>) [/usr/local/lib/node_modules/nw/nwjs/nwjs.app/Contents/Versions/57.0.2987.133/nwjs Framework.framework/libnode.dylib]
 5: node::ContextifyContext::ContextifyContext(node::Environment*, v8::Local<v8::Object>) [/usr/local/lib/node_modules/nw/nwjs/nwjs.app/Contents/Versions/57.0.2987.133/nwjs Framework.framework/libnode.dylib]
 6: node::ContextifyContext::MakeContext(v8::FunctionCallbackInfo<v8::Value> const&) [/usr/local/lib/node_modules/nw/nwjs/nwjs.app/Contents/Versions/57.0.2987.133/nwjs Framework.framework/libnode.dylib]
 7: ChromeMain [/usr/local/lib/node_modules/nw/nwjs/nwjs.app/Contents/Versions/57.0.2987.133/nwjs Framework.framework/nwjs Framework]
 8: v8::FixSourceNWBin(v8::Isolate*, v8::Local<v8::UnboundScript>) [/usr/local/lib/node_modules/nw/nwjs/nwjs.app/Contents/Versions/57.0.2987.133/nwjs Framework.framework/nwjs Framework]
 9: v8::FixSourceNWBin(v8::Isolate*, v8::Local<v8::UnboundScript>) [/usr/local/lib/node_modules/nw/nwjs/nwjs.app/Contents/Versions/57.0.2987.133/nwjs Framework.framework/nwjs Framework]
10: 0x1ed660f84427
11: 0x1ed6611b363f
12: 0x1ed6611aad3b

Issue Analytics

State:
Created 6 years ago
Comments:11 (5 by maintainers)

Top GitHub Comments

1reaction

matthew-deancommented, May 2, 2017

@Christywl Sure, I’ll try to set up a complete mini-project later today. That’s not really a code snippet, but yeah, it would probably help you to have a package.json with the installed modules.

1reaction

matthew-deancommented, May 2, 2017

Just to confirm this isn’t my end, I rolled back NW.js to 0.15.4, and this issue does NOT occur. No “Pointer is not aligned” is thrown.

Also, I had to load this code in a child process to get the binding error (which is how it works in my app). So there’s something that changed with v8 bindings in child processes in NW.js at some point. Please re-open.