Node: Fatal error in ../deps/v8/src/api.cc, line 1051

[muthufmass]

node version 7.3.0, (even tried with 7.4.0, same issue)
react : 15.4.1
gulp : 3.9.0

On running gulp for react js project with node. I get this error. I tried lowering the version less than 7 and lowered all react js versions, then do an npm node-gyp, then things worked, but again moved back to latest on both react and node, things are back to same error.

Any help will be great here, as I am struck on developments.

sh-3.2# gulp

#

Fatal error in ../deps/v8/src/api.cc, line 1051

Check failed: !value_obj->IsJSReceiver() || value_obj->IsTemplateInfo().

#

==== C stack trace ===============================

0   node                                0x0000000100bcb6e3 v8::base::debug::StackTrace::StackTrace() + 19
1   node                                0x0000000100bc8869 V8_Fatal + 233
2   node                                0x00000001001471fa v8::Template::Set(v8::Local<v8::Name>, v8::Local<v8::Data>, v8::PropertyAttribute) + 330
3   fse.node                            0x0000000102789be3 fse::FSEvents::Initialize(v8::Local<v8::Object>) + 197
4   node                                0x00000001009ce69a node::DLOpen(v8::FunctionCallbackInfo<v8::Value> const&) + 854
5   node                                0x000000010017ba9a v8::internal::FunctionCallbackArguments::Call(void (*)(v8::FunctionCallbackInfo<v8::Value> const&)) + 378
6   node                                0x00000001001df93c v8::internal::MaybeHandle<v8::internal::Object> v8::internal::(anonymous namespace)::HandleApiCallHelper<false>(v8::internal::Isolate*, v8::internal::Handle<v8::internal::HeapObject>, v8::internal::Handle<v8::internal::HeapObject>, v8::internal::Handle<v8::internal::FunctionTemplateInfo>, v8::internal::Handle<v8::internal::Object>, v8::internal::BuiltinArguments) + 924
7   node                                0x00000001001ded79 v8::internal::Builtin_Impl_HandleApiCall(v8::internal::BuiltinArguments, v8::internal::Isolate*) + 281
8   ???                                 0x00003771ab1063a7 0x0 + 60961340810151

Need some help.

[addaleax]

This is very, very likely the same kind of problem as described in https://github.com/nodejs/node/issues/9370, so please try to make sure all your dependencies are up to date. If that doesn’t help, you’re probably better off raising this issue at https://github.com/gulpjs/gulp than here.

[addaleax]

I’m closing this as it’s almost certainly not a bug with Node itself, too, but feel free to ask follow-up questions if you have any!

[muthufmass]

i got it fixed.

Ran following commands

npm i -g npm-check-updates
npm-check-updates -u
npm install

Thanks

[Sogl]

@muthufmass Doesn't help me:

Artems-MacBook-Pro:~ Artyom$ npm-check-updates -u
[INFO]: You can also use ncu as an alias
Unhandled rejection TypeError: Path must be a string. Received null
    at assertPath (path.js:7:11)
    at Object.resolve (path.js:1146:7)
    at getPackageDataFromFile (/Users/Artyom/.npm-global-pkg/lib/node_modules/npm-check-updates/lib/npm-check-updates.js:417:33)
    at programRunLocal (/Users/Artyom/.npm-global-pkg/lib/node_modules/npm-check-updates/lib/npm-check-updates.js:407:19)
    at programRun (/Users/Artyom/.npm-global-pkg/lib/node_modules/npm-check-updates/lib/npm-check-updates.js:356:50)
    at tryCatcher (/Users/Artyom/.npm-global-pkg/lib/node_modules/npm-check-updates/node_modules/bluebird/js/release/util.js:16:23)
    at Promise._settlePromiseFromHandler (/Users/Artyom/.npm-global-pkg/lib/node_modules/npm-check-updates/node_modules/bluebird/js/release/promise.js:510:31)
    at Promise._settlePromise (/Users/Artyom/.npm-global-pkg/lib/node_modules/npm-check-updates/node_modules/bluebird/js/release/promise.js:567:18)
    at Promise._settlePromise0 (/Users/Artyom/.npm-global-pkg/lib/node_modules/npm-check-updates/node_modules/bluebird/js/release/promise.js:612:10)
    at Promise._settlePromises (/Users/Artyom/.npm-global-pkg/lib/node_modules/npm-check-updates/node_modules/bluebird/js/release/promise.js:691:18)
    at Promise._fulfill (/Users/Artyom/.npm-global-pkg/lib/node_modules/npm-check-updates/node_modules/bluebird/js/release/promise.js:636:18)
    at Promise._resolveCallback (/Users/Artyom/.npm-global-pkg/lib/node_modules/npm-check-updates/node_modules/bluebird/js/release/promise.js:431:57)
    at Promise._settlePromiseFromHandler (/Users/Artyom/.npm-global-pkg/lib/node_modules/npm-check-updates/node_modules/bluebird/js/release/promise.js:522:17)
    at Promise._settlePromise (/Users/Artyom/.npm-global-pkg/lib/node_modules/npm-check-updates/node_modules/bluebird/js/release/promise.js:567:18)
    at Promise._settlePromise0 (/Users/Artyom/.npm-global-pkg/lib/node_modules/npm-check-updates/node_modules/bluebird/js/release/promise.js:612:10)
    at Promise._settlePromises (/Users/Artyom/.npm-global-pkg/lib/node_modules/npm-check-updates/node_modules/bluebird/js/release/promise.js:691:18)

node 7.4.0
npm 4.2.0

[funcelot]

npm i -g npm-check-updates
npm-check-updates -u
npm install

Works!

[funcelot]

for windows create empty .npmrc to compile against VS2015, if any:

cd %USERPROFILE%
echo msvs_version=2015>.npmrc

[lvl99]

I continue to get the error but at a different line number:

#
# Fatal error in ../deps/v8/src/api.cc, line 1200
# Check failed: !value_obj->IsJSReceiver() || value_obj->IsTemplateInfo().
#

I ran the npm-check-updates and also cleared the node_modules folder and cleared the npm cache too.

[bnoordhuis]

@lvl99 You probably have a native module somewhere that hasn't updated its code. The stack trace should show where the offending call came from (on UNIX - native stack traces aren't implemented on Windows.)

[NaruFGT]

I have a similar issue on Node v8.1.4

#
# Fatal error in ../deps/v8/src/api.cc, line 1200
# Check failed: !value_obj->IsJSReceiver() || value_obj->IsTemplateInfo().
#

I believe it is a pg-native problem for me. I'll add more info if I resolve the problem.

Edit:
I updated to a newer version of node, npm install'ed the dependencies which effectively updated them. The error vanished.
npm ls didn't seem to help me. I relied on package.json bundled with what I was working on to show me what to update. Hope this helps someone else.

[godoakbrutal]

@muthufmass You just save my day.

[crcali]

I am getting a similar problem. I tried all the above solutions, but none of them were working.
Here is my error message:

#

Fatal error in ../deps/v8/src/api.cc, line 1248

Check failed: !value_obj->IsJSReceiver() || value_obj->IsTemplateInfo().

#

[antoniobrandao]

The above solutions didn't work for me.

My problem was this part in my package.json:

"engines": {
    "node": "4.8.4"
},

Which was causing the same error output as @crcali mentioned in the previous comment.

[dddrey]

@antoniobrandao did it help you?
cas i had this line as well, but removing it changed nothing

[antoniobrandao]

@Andrushkins the problem was the Node version I was running. In my case removing that instruction from the package.json helped for one project, but it didn't help for another.

My final solution was to use the "n" package to switch between different Node versions accordingly.

In my case, some of my projects require that I am running Node 4.x, and others work with the latest stable version.

So in the end, I restored that instruction to my package.json of the project, since this project in particular requires that I use Node 4.8.4.

Always make sure to be running the appropriate Node version the project you're working with.

It would be nice if Node programs could throw a more comprehensible error, eg. "Incompatible Node version".

---

Until then, whenever you see errors with "v8" in it, most likely you're running a project against an incompatible version of node.

[skerit]

I'm getting this error:

# Fatal error in ../deps/v8/src/api.cc, line 1248
# Check failed: !value_obj->IsJSReceiver() || value_obj->IsTemplateInfo().
#
Illegal instruction

I removed the node_modules folder & reinstalled everything using v8.9.3 & v8.11.3, both installed using n. But I get the same error every time, but only on my production server.

On my local ubuntu machine everything runs fine. My colleague is even running it on MacOS without any issues :/

[addaleax]

@skerit Can you open a new issue and include more information, for example steps to reproduce?

[wangwenj]

@skerit I'm getting the error same as you.Can you help me ?