Skip to content

shwap/bitswap: Memory leak #4151

Open
Open
@Wondertan

Description

@Wondertan

Image

This branch contains changes that minimized the affect for the leak, but didn't completely solved.

The main hunch is related to high peer churn, as with stable connections this is not reproducible. Also, this is demonstrated by ipfs/boxo@4becbe1, which was the commit that fixed alleviated the most pressure. This commit avoids automatic WANT_HAVE broadcast to every connected peer, relying on internal rebroadcast inside session instead.

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't working

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions