Skip to content

Memory leak in consensus #363

@ebuchman

Description

@ebuchman

Monitoring the memory usage while running the consensus tests suggests there might be a leak somewhere as we quickly balloon above a few GB of RAM.

This recently caused unexpected failures on Circle as the used memory climbed above 4 GB (the max there). Adding stopConsensusNet function to shutdown reactors seemed to roughly halve the memory usage, but it seems like we should be able to do better.

Metadata

Metadata

Assignees

No one assigned

    Labels

    C:consensusComponent: ConsensusT:bugType Bug (Confirmed)

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions