Error: Exited unexpectedly with code: 139

1

Specifically on Node 6/7, I’m getting an error with only an error code.

require('@citation-js/core')

Exited unexpectedly with code: 139

RunKit

I think this corresponds to

node: ../deps/uv/src/unix/core.c:182: uv_close: Assertion `0' failed.
Aborted (core dumped)

Any ideas?

2

Hey there!

This usually happens when the node process crashes. This can happen for a variety of reasons.

3

Yeah, I’m just trying to figure out why because it was working fine earlier. Two CI jobs, on the same commit:

And it isn’t some weird Travis-CI thing either (like the cache they enabled by default for npm this July) because it doesn’t work here either (pinned that down to sync-request by the way).

4

Well, I found the problem (it was on my end). Both 75a57ad and 92eaaf5 in the sync-rpc sub-dependency break, on their own, Node 6 support. And it was in a patch-level version bump on, so I didn’t notice the difference.