Segment library crashes Node 14: upgrade Node, not the SDK

TL;DR

If a Node service using analytics-node crashes with STATUSSTACKBUFFER_OVERRUN, check the Node version first: on Node 14 this was an upstream axios interaction, and the fix is to upgrade Node to 16 or later rather than ripping out the Segment library.

Steps

1. If a Node service using analytics-node crashes with STATUSSTACKBUFFER_OVERRUN, check the Node version first: on Node 14 this was an upstream axios interaction, and the fix is to upgrade Node to 16 or later rather than ripping out the Segment library. When pinning runtimes for agent-deployed backends, prefer current LTS majors and treat exit code -1073740791 as a runtime bug signature, not an application bug.

When to use

You are seeing this: When pinning runtimes for agent-deployed backends, prefer current LTS majors and treat exit code -1073740791 as a runtime bug signature, not an application bug. Use this skill when you run into "Segment library crashes Node 14: upgrade Node, not the SDK".

When not to use

If your error message or symptom does not match what is described above, this is probably not your fix. Search for your exact error text instead of forcing this one to fit.

Versions

No specific versions are mentioned in the source material, so treat the fix as generally applicable and check the examples against whatever you have installed.

Why this happens

The original report does not dig into a root cause. It documents the symptom and the fix that resolved it.

Source: GitHub issue segmentio/analytics-node#302 (closed, 5 comments): a Node.js 14 service on Azure Functions crashed intermittently with node exited with code -1073740791, STATUSSTACKBUFFER_OVERRUN. The reporter traced it to an upstream axios bug triggered by the library's basic-auth HTTP requests (axios/axios#3396, rooted in a Node issue), not to Segment's code or to Azure Functions. Segment kept the auth change in the backlog as low priority; the reporter resolved it permanently by upgrading to Node.js 16 as soon as Azure Functions supported it, after which the crashes stopped.

Verified resolution: If a Node service using analytics-node crashes with STATUSSTACKBUFFER_OVERRUN, check the Node version first: on Node 14 this was an upstream axios interaction, and the fix is to upgrade Node to 16 or later rather than ripping out the Segment library. When pinning runtimes for agent-deployed backends, prefer current LTS majors and treat exit code -1073740791 as a runtime bug signature, not an application bug.

Source URL: https://github.com/segmentio/analytics-node/issues/302