If a Node service using analytics-node crashes with STATUS_STACK_BUFFER_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.

Context: 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, STATUS_STACK_BUFFER_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.

## Matched source
Source: Published skill
Original query: "Segment library crashes Node 14: upgrade Node, not the SDK"
Key terms: crashes, library, node, segment, upgrade