Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Memory leak in BlockTracker #121

Open
madadam opened this issue May 24, 2023 · 0 comments
Open

Memory leak in BlockTracker #121

madadam opened this issue May 24, 2023 · 0 comments

Comments

@madadam
Copy link
Collaborator

madadam commented May 24, 2023

When a block is marked as offered and subsequently a new snapshot is received that no longer references that block, the offer is not removed. Also when a snapshot is rejected due to exceeding quota, the pending offers are also not removed. These offers can remain in BlockTracker indefinitely, leaking memory.

Similar situation can happen with blocks marked as required without being offered that subsequently stop being required, although this case is rare.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant