Segmentation Fault

[furkanmustafa]

• Version: 6.5.0
• Platform: Linux thehostname 4.7.2 #21 SMP Fri Aug 26 03:23:44 UTC 2016 x86_64 GNU/Linux

I'm not exacly sure what's the main reason for this crash is, therefore I don't have a way to replicate. My application is quite simple and doesn't have any native modules. General outline is, the app connects to Mongo & Redis, uses babel, and is a simple background worker for kue tasks. Application works well for a while, and then segfaults.

Here is the coredumps;

Process 32573 (node) of user 1000 dumped core.

  Stack trace of thread 32573:
  #0  0x00007f198dd32367 kill (libc.so.6)
  #1  0x00007f198fe84ea9 uv_kill (libuv.so.1)
  #2  0x0000000000d68ae0 _ZN4node4KillERKN2v820FunctionCallbackInfoINS0_5ValueEEE (node)
  #3  0x00000000006f7bd1 _ZN2v88internal25FunctionCallbackArguments4CallEPFvRKNS_20FunctionCallbackInfoINS_5ValueEEEE (node)
  #4  0x000000000074d9ab n/a (node)
  #5  0x000000000074e078 n/a (node)
  #6  0x000000000074e1de n/a (node)
  #7  0x00000c3b85b092a7 n/a (n/a)

Process 32555 (npm) of user 1000 dumped core.

  Stack trace of thread 32555:
  #0  0x00007f8074ef5367 kill (libc.so.6)
  #1  0x00007f8077047ea9 uv_kill (libuv.so.1)
  #2  0x0000000000d68ae0 _ZN4node4KillERKN2v820FunctionCallbackInfoINS0_5ValueEEE (node)
  #3  0x00000000006f7bd1 _ZN2v88internal25FunctionCallbackArguments4CallEPFvRKNS_20FunctionCallbackInfoINS_5ValueEEEE (node)
  #4  0x000000000074d9ab n/a (node)
  #5  0x000000000074e078 n/a (node)
  #6  0x000000000074e1de n/a (node)
  #7  0x00002e45f53092a7 n/a (n/a)

Process 32579 (node) of user 1000 dumped core.

  Stack trace of thread 32579:
  #0  0x0000000000989f95 _ZN2v88internal9FieldType7AsClassEv (node)
  #1  0x000000000098a0f4 _ZN2v88internal9FieldType7ConvertEPNS0_4ZoneE (node)
  #2  0x0000000000787c8b _ZN2v88internal8compiler17AccessInfoFactory25ComputePropertyAccessInfoENS0_6HandleINS0_3MapEEENS3_INS0_4NameEEENS1_10
AccessModeEPNS1_18PropertyAccessInfoE (node)
  #3  0x000000000078831e _ZN2v88internal8compiler17AccessInfoFactory26ComputePropertyAccessInfosERKNS0_4ListINS0_6HandleINS0_3MapEEENS0_25Free
StoreAllocationPolicyEEENS4_INS0_4NameEEENS1_10AccessModeEPNS0_10ZoneVectorINS1_18PropertyAccessInfoEEE (node)
  #4  0x00000000007f9566 _ZN2v88internal8compiler29JSNativeContextSpecialization17ReduceNamedAccessEPNS1_4NodeES4_RKNS0_4ListINS0_6HandleINS0_
3MapEEENS0_25FreeStoreAllocationPolicyEEENS6_INS0_4NameEEENS1_10AccessModeENS0_12LanguageModeES4_ (node)
  #5  0x00000000007fb3af _ZN2v88internal8compiler29JSNativeContextSpecialization17ReduceNamedAccessEPNS1_4NodeES4_RKNS0_13FeedbackNexusENS0_6H
andleINS0_4NameEEENS1_10AccessModeENS0_12LanguageModeE (node)
  #6  0x00000000007fb43f _ZN2v88internal8compiler29JSNativeContextSpecialization17ReduceJSLoadNamedEPNS1_4NodeE (node)
  #7  0x00000000007fda15 _ZN2v88internal8compiler29JSNativeContextSpecialization6ReduceEPNS1_4NodeE (node)
  #8  0x00000000007ca506 _ZN2v88internal8compiler12GraphReducer6ReduceEPNS1_4NodeE (node)
  #9  0x00000000007caf5c _ZN2v88internal8compiler12GraphReducer9ReduceTopEv (node)
  #10 0x00000000007cb088 _ZN2v88internal8compiler12GraphReducer10ReduceNodeEPNS1_4NodeE (node)
  #11 0x00000000008325ed _ZN2v88internal8compiler8Pipeline12GenerateCodeEv (node)
  #12 0x00000000008895a2 _ZN2v88internal19OptimizedCompileJob11CreateGraphEv (node)
  #13 0x000000000088a945 n/a (node)
  #14 0x000000000088b6d9 _ZN2v88internal8Compiler16CompileOptimizedENS0_6HandleINS0_10JSFunctionEEENS1_15ConcurrencyModeE (node)
  #15 0x0000000000b63e05 _ZN2v88internal35Runtime_CompileOptimized_ConcurrentEiPPNS0_6ObjectEPNS0_7IsolateE (node)
  #16 0x0000073eda9092a7 n/a (n/a)

[addaleax]

• Does this happen with earlier versions of Node, too?
• Where did you get the Node v6.5.0 binary from?
• It looks like this is some script being run by npm… I assume the fault also occurs when running the script directly?

[addaleax]

Also, could you try running this with a debug build of node?

[furkanmustafa]

Does this happen with earlier versions of Node, too?

Tested with v5.10.1 and survived far more, looks like not going to crash.
Will test with v6.4.0 and debug build of v6.5.0

Where did you get the Node v6.5.0 binary from?

Arch Linux

It looks like this is some script being run by npm… I assume the fault also occurs when running the script directly?

Got rid of npm start, started with ./node_modules/.bin/babel-node src/Server.js directly. Still the same result without the npm's stack trace.

Also, could you try running this with a debug build of node?

Do I need to build it myself or is there an official debug build of node somewhere I can download or a docker image?

[addaleax]

Do I need to build it myself or is there an official debug build of node somewhere I can download or a docker image?

I think you’d have to build it yourself, ./configure --debug && make -j4 should give you a node_g debug executable. And in this case, I’m even more sure that you’ll have to build yourself, given that Arch seems to be the only platform to provide v6.5.0 at this point (there aren’t even official Node v6.5.0 binaries out yet).

[jbergstroem]

I just had a question on IRC wrt missing -headers for npm bundled with Node.js 6.5.0 in Archlinux too. Perhaps we should check in with them and see if we can align releases?

[MylesBorins]

6.5.0 has not been promoted yet, which is why the headers are not available

On Sun, Aug 28, 2016, 4:03 PM Johan Bergström notifications@github.com
wrote:

I just had a question on IRC wrt missing -headers for npm bundled with
Node.js 6.5.0 in Archlinux too. Perhaps we should check in with them and
see if we can align releases?

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
#8310 (comment), or mute
the thread
https://github.com/notifications/unsubscribe-auth/AAecV43SgiC04rTBF8vYRvC4lc3u0PLgks5qkbFegaJpZM4Ju7M-
.

[jbergstroem]

@thealphanerd yeah, I know. I just emailed the maintainer in Archlinux about this and queried if he could align the releases with ours.

[furkanmustafa]

Looks like v6.4.0 (docker image 6-slim) also does not crash.
I have compiled node v6.5.0 with --debug flag (inside the same docker image), and that also did not crash.

I believe that makes this an Arch Linux issue, probably one of the shared libraries.

I'll try playing with it a little bit more.

[addaleax]

I believe that makes this an Arch Linux issue, probably one of the shared libraries.

Sounds quite possible… somebody else is experience very similar difficulties on Arch (almost identical stack trace) in npm/npm#13782

[moki]

Experienced problems after upgrading node to 6.5 on arch as well, rolling back to 6.4 solves the issue tho.

[addaleax]

fwiw, I’ve set up Arch Linux in a VM, but couldn’t reproduce any problems so far… do you have something like reproducible test cases you could share (even if they are large) or something in that direction?

[moki]

@addaleax Apricity OS Arch distro update to node with packman from 6.4 to 6.5 leads to problem, rollback solves issue that's all i've got. Point me in some direction, how can i help work this out.

[mscdex]

You could checkout the node source from git and do a git bisect between the v6.4.0 and v6.5.0 tags. I suspect it will be the upgrade to V8 5.1 though, it looks like it may be a bug there.