Memory not released (maybe related to high webhook request count?)
Open
Nobody has claimed this yet.
bug
needs investigation
- Dominant language
- Elixir
- Stars
- 296
- Forks
- 86
- Avg merge
- 1d 13h
- Merged PRs (30d)
- 50
Description
Needs investigation
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 by examining the attached memory report and investigating whether the high webhook request count correlates with memory growth. Reproduce the behavior if possible, then trace the relevant webhook handling flow. Done means identifying the cause and demonstrating that memory is released or usage no longer grows unexpectedly.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- elixir
- Domain
- backend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100