marigold-dev / marigold-dev/deku
clean mempool to prevent memory leaks
Open
Nobody has claimed this yet.
backlog
- Dominant language
- OCaml
- Stars
- 82
- Forks
- 17
- PR merge metrics
- No merged PRs in 30d
Description
Currently the sidechain node has a memory leak as we don't clean the mempool, leading to couple gigabytes of usage after days.
This is easily solved by restarting the node, but it's non ideal.
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 tracing how the sidechain node creates, retains, and clears its mempool, then inspect the restart behavior described in the issue. Done means the mempool no longer grows to gigabytes over several days and the node does not require restarting to reclaim that memory.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- ocaml
- Domain
- blockchain
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100