Skip to content

asObservable leaks #115

Description

@ericeslinger

https://github.com/plumpstack/plump/pull/114 added a per-plump cache of read subjects, as the read subjects are a bit expensive to build, tear down, and end up duplicating a lot of effort. The subjects themselves are refcounted, so they don't leak heavily, but they do leak a little.

what should happen is that there should be a separate garbage collector process that runs on a setInterval that examines each and decides whether or not to delete it - how many observers does it have? when was it last touched? make an LRU cache that can conditionally delete basically.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions