Node 22 on armvc6 and armv7 get into an out of memory infinite loop
Open
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 122k
- Forks
- 37.3k
- Avg merge
- 4d 2h
- Merged PRs (30d)
- 283
Description
Version
22
Platform
Linux 431b32e3d8c4 6.6.31-linuxkit #1 SMP Thu May 23 08:36:57 UTC 2024 armv7l Linux
Subsystem
No response
What steps will reproduce the bug?
docker run --cap-add=SYS_PTRACE -e QEMU_STRACE=1 --rm -it --platform linux/arm/v6 node:22-alpine
How often does it reproduce? Is there a required condition?
Every time
What is the expected behavior? Why is that the expected behavior?
Container starts
What do you see instead?
Without trace, the container just hangs, with tracing the following log is output forever
mremap(1081462784,4096,8192,0,0,1082133536) = -1 errno=12 (Out of memory)
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
Start by running the provided docker command for node:22-alpine with --platform linux/arm/v6, first without tracing and then with QEMU_STRACE=1. Investigate the repeated mremap failure and out-of-memory loop on armv6 and armv7. Done means the Node 22 container starts instead of hanging indefinitely on these platforms.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, linux, nodejs
- Domain
- devops, operating-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100