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

node crashes on startup, but only when run from emacs #6870

Closed
tomjakubowski opened this issue May 19, 2016 · 2 comments
Closed

node crashes on startup, but only when run from emacs #6870

tomjakubowski opened this issue May 19, 2016 · 2 comments
Labels
duplicate Issues and PRs that are duplicates of other issues or PRs.

Comments

@tomjakubowski
Copy link

  • node version: 6.1.0 (installed via Homebrew)
  • platform: Darwin tjakubowskimbp.xxxxxxx 15.4.0 Darwin Kernel Version 15.4.0: Fri Feb 26 22:08:05 PST 2016; root:xnu-3248.40.184~3/RELEASE_X86_64 x86_64
  • emacs version: GNU Emacs 25.0.92.1

I recently upgraded from node 5.7.0 to node 6.1.0. Since upgrading, node crashes on startup but only when run from within emacs (eshell, shell-mode, compilation-mode, whatever). All is well if node is executed from zsh running in iTerm2.

Here's a backtrace:

(lldb) bt
bt
* thread #1: tid = 0x4151cf, 0x00007fff980cbf06 libsystem_kernel.dylib`__pthread_kill + 10, queue = 'com.apple.main-thread', stop reason = signal SIGABRT
  * frame #0: 0x00007fff980cbf06 libsystem_kernel.dylib`__pthread_kill + 10
    frame #1: 0x00007fff8b0ee4ec libsystem_pthread.dylib`pthread_kill + 90
    frame #2: 0x00007fff9fb896e7 libsystem_c.dylib`abort + 129
    frame #3: 0x000000010071770d node`uv_thread_create + 237
    frame #4: 0x000000010070b1da node`init_once + 266
    frame #5: 0x00007fff8b0ebbf6 libsystem_pthread.dylib`__pthread_once_handler + 65
    frame #6: 0x00007fff9e47afc4 libsystem_platform.dylib`_os_once + 41
    frame #7: 0x00007fff8b0ebb95 libsystem_pthread.dylib`pthread_once + 57
    frame #8: 0x0000000100717904 node`uv_once + 9
    frame #9: 0x000000010070b0b4 node`uv__work_submit + 42
    frame #10: 0x0000000100710067 node`uv_fs_open + 253
    frame #11: 0x00000001005f9310 node`node::Open(v8::FunctionCallbackInfo<v8::Value> const&) + 885
    frame #12: 0x00000001001742fb node`v8::internal::FunctionCallbackArguments::Call(void (*)(v8::FunctionCallbackInfo<v8::Value> const&)) + 371
    frame #13: 0x000000010019e5f2 node`v8::internal::MaybeHandle<v8::internal::Object> v8::internal::(anonymous namespace)::HandleApiCallHelper<false>(v8::internal::Isolate*, v8::internal::(anonymous namespace)::BuiltinArguments<(v8::internal::BuiltinExtraArguments)1>) + 992
    frame #14: 0x00000001001ac256 node`v8::internal::Builtin_HandleApiCall(int, v8::internal::Object**, v8::internal::Isolate*) + 105
    frame #15: 0x00002ce39c00961b
    frame #16: 0x00002ce39c177854
    frame #17: 0x00002ce39c00d157
    frame #18: 0x00002ce39c176279
    frame #19: 0x00002ce39c1506df
    frame #20: 0x00002ce39c00d157
    frame #21: 0x00002ce39c040a7e
    frame #22: 0x00002ce39c03e4f2
    frame #23: 0x00002ce39c037f84
    frame #24: 0x00002ce39c022922
    frame #25: 0x0000000100336bc0 node`v8::internal::(anonymous namespace)::Invoke(v8::internal::Isolate*, bool, v8::internal::Handle<v8::internal::Object>, v8::internal::Handle<v8::internal::Object>, int, v8::internal::Handle<v8::internal::Object>*, v8::internal::Handle<v8::internal::Object>) + 406
    frame #26: 0x000000010033695b node`v8::internal::Execution::Call(v8::internal::Isolate*, v8::internal::Handle<v8::internal::Object>, v8::internal::Handle<v8::internal::Object>, int, v8::internal::Handle<v8::internal::Object>*) + 459
    frame #27: 0x000000010015d669 node`v8::Function::Call(v8::Local<v8::Context>, v8::Local<v8::Value>, int, v8::Local<v8::Value>*) + 417
    frame #28: 0x00000001005df9b7 node`node::LoadEnvironment(node::Environment*) + 625
    frame #29: 0x00000001005e0f3e node`node::Start(int, char**) + 517
    frame #30: 0x0000000100001f34 node`start + 52
(lldb) ^D

Originally filed here: nodejs/node-gyp#934

@tomjakubowski
Copy link
Author

Oops, I didn't know there was a 6.2.0 release. And upgrading seems to have resolved this issue.

@tomjakubowski
Copy link
Author

looks like this was the same as #6563

@ChALkeR ChALkeR added the duplicate Issues and PRs that are duplicates of other issues or PRs. label Jun 1, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
duplicate Issues and PRs that are duplicates of other issues or PRs.
Projects
None yet
Development

No branches or pull requests

2 participants