status 137 (out of memory) on heroku
Open
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 16.6k
- Forks
- 1.6k
- PR merge metrics
- No merged PRs in 30d
Description
since 24.02 chisel v 1.7.7, which runs in free heroku container dyno, starts to crash with status 137. rollback to v 1.6.0 helped to resolve this problem
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
No files or tests are identified. Compare chisel v1.7.7 with v1.6.0 and reproduce the failure in a free Heroku container dyno, focusing on the change that causes status 137; done means the dyno no longer crashes with an out-of-memory exit.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- networking
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100