crypto-org-chain / crypto-org-chain/cronos
Problem: potential memory leaks in the archive node
Open
- Dominant language
- Go
- Stars
- 336
- Forks
- 299
- Avg merge
- 2d 17h
- Merged PRs (30d)
- 4
Description
There are users experiencing potential memory leaks in archive nodes with both rocksdb and pebble backends, need to investigate.
Contributor guide
Research direction
The issue concerns memory leaks in archive nodes using RocksDB and Pebble, but names no files, tests, or entry points. Begin by locating the archive-node storage integrations and establishing a reproducible memory-growth case; done means identifying the leak and adding regression coverage for both backends.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- backend, blockchain, databases
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100