Node: core dump during postinstall script with node v10.0.0

Created on 25 Apr 2018  路  7Comments  路  Source: nodejs/node

  • Version: v10.0.0
  • Platform: Linux ip-10-0-0-205 4.4.0-116-generic #140-Ubuntu SMP Mon Feb 12 21:23:04 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux
  • Subsystem:

Everything worked fine with node v8.x
I don't know exactly where, but somewhere in my postinstall script on a special jenkins vm, something gets wrong...
I have no tooling to analyze the core dump, can someone have a look at it?

node[3772]: ../src/node_contextify.cc:631:static void node::contextify::ContextifyScript::New(const v8::FunctionCallbackInfo<v8::Value>&): Assertion `args[1]->IsString()' failed.
 1: node::Abort() [node]
 2: 0x87b6c5 [node]
 3: node::contextify::ContextifyScript::New(v8::FunctionCallbackInfo<v8::Value> const&) [node]
 4: v8::internal::FunctionCallbackArguments::Call(v8::internal::CallHandlerInfo*) [node]
 5: 0xad5b9f [node]
 6: v8::internal::Builtin_HandleApiCall(int, v8::internal::Object**, v8::internal::Isolate*) [node]
 7: 0x86daa40427d
Aborted (core dumped)
vm wrong repo

Most helpful comment

I fixed this by running 'yarn'

All 7 comments

I can't check the core dump right now but my guess would be that you have code somewhere, possibly in a dependency, that uses process.binding('contextify') directly.

Yes, can confirm via https://github.com/EvanOxfeld/node-unzip dependency
-> https://github.com/npm/fstream
-> https://github.com/isaacs/node-graceful-fs
-> https://github.com/addaleax/natives/blob/master/index.js#L12

Right, I see there's already at least one open issue about moving away from natives. I'll close this out because it's not our bug to fix; you might want to chime in on the other bug report.

ok, thx

I updated "grunt-bower-task": "0.4.0", to "grunt-bower-task": "0.5.0", and that fixed it for me, based on the deprecation notice here https://www.npmjs.com/package/natives

I fixed this by running 'yarn'

After running yarn as @BB-000 suggested I got another problem. It was solved by rebuilding node-sass via npm rebuild node-sass. Hope it helps someone!

Was this page helpful?
0 / 5 - 0 ratings

Related issues

seishun picture seishun  路  3Comments

cong88 picture cong88  路  3Comments

Icemic picture Icemic  路  3Comments

dfahlander picture dfahlander  路  3Comments

srl295 picture srl295  路  3Comments