Skip to content

Croniter has memory leak #362

@conanjen

Description

@conanjen

Was trying to upgrade past 0.17.3 but couldn't figure out why uv wasn't resolving past it and realized there's a requirement to croniter >= 6. Not sure if you've run into this or noticed it, but on our production deployments with croniter we've had to hold it to 5.0.1 in order to avoid this: pallets-eco/croniter#182.

Unsure if it's worth modifying on docket to hold as well until they actually prep a release that includes the fix they've already merged that addresses it, but figured it would be worth bringing to everyone's attention before they spend a bunch of time attempting to determine where they're leaking memory from.

Additionally, it looks like there's another memory leak with PR open right now that is awaiting maintainer response for a similar situation: pallets-eco/croniter#195.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions