ChainSafe / ChainSafe/lodestar
Network Processor may leak messages on awaiting queues
- Dominant language
- TypeScript
- Stars
- 1.4k
- Forks
- 483
- Avg merge
- 1d 16h
- Merged PRs (30d)
- 150
Description
### Describe the bug
```
2026-06-27 14:52 UTC: FATAL ERROR: Ineffective mark-compacts near heap limit — JavaScript heap out of memory
```
### Expected behavior
queued messages of network processor should be pruned by slot
### Steps to reproduce
_No response_
### Additional context
_No response_
### Operating system
Linux
### Lodestar version or commit hash
glamsterdam-devnet-6
Contributor guide
Research direction
Start by tracing the network processor's awaiting queues and how queued messages are assigned and pruned by slot. Use the glamsterdam-devnet-6 context and the reported heap exhaustion to investigate retention; done means queued messages are pruned by slot without remaining until out-of-memory failure.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- distributed-systems, networking
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 45/100