Skip to content

Continuous memory leak with console_subscriber #184

Closed
@Seppel3210

Description

@Seppel3210

When calling console_subscriber::init() there is a big memory leak that seems to grow faster the more futures are spawned.
I ran this application through valgrind and it said that all the blocks were still reachable (the pointers still exist) so I'm guessing it's some sort of Circular ref-counted data structure that isn't using Weak properly (or something equivalent).

When I commented out the console_subscriber::init() line the leak completely went away (now idling at 3mb when it would go to 252mb when running for a couple hours with the subscriber)

Metadata

Metadata

Assignees

No one assigned

    Labels

    C-subscriberCrate: console-subscriber.S-bugSeverity: bug

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions