stack size exceeded on M1/arm64 but not on x86
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 122k
- Forks
- 37.3k
- Avg merge
- 4d 2h
- Merged PRs (30d)
- 283
Description
Version
v16.13.1
Platform
Darwin USAGPM.local 21.2.0 Darwin Kernel Version 21.2.0: Sun Nov 28 20:28:41 PST 2021; root:xnu-8019.61.5~1/RELEASE_ARM64_T6000 arm64
Subsystem
No response
What steps will reproduce the bug?
I have a project with about 1000 typescript files (it's private so I can't point you at it, sorry). It's a react project that uses create-react app.
The arm version of v16 gives:
Failed to compile.
undefined
fork-ts-checker-webpack-plugin error in undefined(undefined,undefined):
Maximum call stack size exceeded TSINTERNAL
The x86 version works fine. I've tried every arm version of v16 that I can find, all have the same issue, every x86 version works with no problem. Running yarn tsc explicitly works fine with both the arm and the x86 version.
How often does it reproduce? Is there a required condition?
With the affected project it happens 100% of the time, with other projects I can't reproduce this.
What is the expected behavior?
x86 and arm behavior should be identical.
What do you see instead?
No response
Additional information
No response
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The report names Node v16.13.1 on Darwin arm64, a React/Create React App project, and yarn tsc, but provides no source file, test, or public reproduction. Start by reproducing the failure on arm64 versus x86 with the affected project and compare it with explicit yarn tsc; done means isolating a reproducible runtime or toolchain cause.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- node.js, react, typescript
- Domain
- build-system, operating-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100