processone / processone/eturnal
Debian13: eturnal 1.12.x allocates >2 GB of memory at launch
Open
Nobody has claimed this yet.
containers
- Dominant language
- Erlang
- Stars
- 342
- Forks
- 25
- PR merge metrics
- No merged PRs in 30d
Description
I'm using the Docker image, and granting 2 GB of memory leads to OOM (code 137). Versions before 1.12 were fine with 128 MB.
I have no active TURN sessions:
eturnal 1.12.2 on Erlang/OTP 27 (ERTS 15.2.7.1)
Uptime: 0 days, 0 hours, 2 minutes, 23 seconds
Active TURN sessions: 0
Processes: 81
Total length of run queues: 1
Total CPU usage (reductions): 1779034
Allocated memory (MiB): 2093
Contributor guide
No contributing guide indexed for this repository
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 with the Docker image for eturnal 1.12.2 on Erlang/OTP 27 and compare launch behavior with a pre-1.12 version. Reproduce the no-session startup case and inspect the reported allocated memory; done means identifying the regression and confirming startup stays below the available 2 GB without OOM.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, erlang
- Domain
- backend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100