node crashes on grunt-ts watch task when ts file change is detected

Created on 30 Oct 2016  路  2Comments  路  Source: nodejs/node

  • 7.0.0:
  • *_Darwin 16.1.0 Darwin Kernel Version 16.1.0: Thu Oct 13 21:26:57 PDT 2016; root:xnu-3789.21.3~60/RELEASE_X86_64 x86_64
    *_:
  • Subsystem:
    grunt-cli v1.2.0
    grunt v1.0.1
     Fatal error in ../deps/v8/src/api.cc, line 1051
     Check failed: !value_obj->IsJSReceiver() || value_obj->IsTemplateInfo().
    ==== C stack trace ===============================
        0   node                                0x0000000100b8db23 v8::base::debug::StackTrace::StackTrace() + 19
        1   node                                0x0000000100b8aca9 V8_Fatal + 233
        2   node                                0x0000000100147cfa v8::Template::Set(v8::Local<v8::Name>, v8::Local<v8::Data>, v8::PropertyAttribute) + 330
        3   fse.node                            0x00000001027c3c33 fse::FSEvents::Initialize(v8::Local<v8::Object>) + 197
        4   node                                0x00000001009ce0bc node::DLOpen(v8::FunctionCallbackInfo<v8::Value> const&) + 854
        5   node                                0x000000010017c59a v8::internal::FunctionCallbackArguments::Call(void (*)(v8::FunctionCallbackInfo<v8::Value> const&)) + 378
        6   node                                0x00000001001e029c 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                                0x00000001001df6d9 v8::internal::Builtin_Impl_HandleApiCall(v8::internal::BuiltinArguments, v8::internal::Isolate*) + 281
        8   ???                                 0x00000a42ffa063a7 0x0 + 11282872820647
addons macos

Most helpful comment

This doesn鈥檛 look like a bug in Node core (or in grunt) to me. As far as I can tell, you seem to be using an old version of the fsevents package, which uses what has been a deprecated V8 feature, that got removed in Node v7.

Please make sure npm ls | grep fsevents lists the latest version of fsevents (1.0.14), and if it doesn鈥檛, update your dependencies.

All 2 comments

This doesn鈥檛 look like a bug in Node core (or in grunt) to me. As far as I can tell, you seem to be using an old version of the fsevents package, which uses what has been a deprecated V8 feature, that got removed in Node v7.

Please make sure npm ls | grep fsevents lists the latest version of fsevents (1.0.14), and if it doesn鈥檛, update your dependencies.

Judging from the issue title, there鈥檚 a good chance you鈥檙e running into https://github.com/TypeStrong/grunt-ts/issues/369. I鈥檓 closing this as it鈥檚 very likely not a bug with Node, but feel free to ask follow-up questions if you have any!

Was this page helpful?
0 / 5 - 0 ratings

Related issues

Brekmister picture Brekmister  路  3Comments

vsemozhetbyt picture vsemozhetbyt  路  3Comments

danialkhansari picture danialkhansari  路  3Comments

Icemic picture Icemic  路  3Comments

dfahlander picture dfahlander  路  3Comments