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

illegal hardware instruction when running hexo #2361

Closed
NetOpWibby opened this issue Jan 18, 2017 · 4 comments
Closed

illegal hardware instruction when running hexo #2361

NetOpWibby opened this issue Jan 18, 2017 · 4 comments

Comments

@NetOpWibby
Copy link

NetOpWibby commented Jan 18, 2017

before you submit your issue, please delete all the example code in template

Environment Info

v7.4.0

BUG

I believe this is an issue with node 7, which I just updated to last week. I didn't think anything of it because I could with node.js on a regular basis. Wanting to work on a blog post, I decided to fire up Hexo and this is what I saw.

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

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

    0   node                                0x0000000100bcd343 v8::base::debug::StackTrace::StackTrace() + 19
    1   node                                0x0000000100bca4c9 V8_Fatal + 233
    2   node                                0x0000000100147afa v8::Template::Set(v8::Local<v8::Name>, v8::Local<v8::Data>, v8::PropertyAttribute) + 330
    3   fse.node                            0x0000000105f59c33 fse::FSEvents::Initialize(v8::Local<v8::Object>) + 197
    4   node                                0x00000001009cf029 node::DLOpen(v8::FunctionCallbackInfo<v8::Value> const&) + 854
    5   node                                0x000000010017c39a v8::internal::FunctionCallbackArguments::Call(void (*)(v8::FunctionCallbackInfo<v8::Value> const&)) + 378
    6   node                                0x00000001001e023c 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                                0x00000001001df679 v8::internal::Builtin_Impl_HandleApiCall(v8::internal::BuiltinArguments, v8::internal::Isolate*) + 281
    8   ???                                 0x00002a06eed063a7 0x0 + 46209264804775
    9   ???                                 0x00002a06eee95b7a 0x0 + 46209266441082
[1]    32842 illegal hardware instruction  hexo generate --debug
@NoahDragon
Copy link
Member

Could you please delete the node_modules folder and run npm install?

@NetOpWibby
Copy link
Author

I did that before making this issue and just tried it again. No dice.

@NoahDragon
Copy link
Member

Here is a solution I found in another issue nodejs/node#10659

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

@NetOpWibby
Copy link
Author

Haha, I actually did that as well! ncu is an awesome plugin. Still didn't fix my issue.

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

2 participants