Skip to content

Memory Leak in parse_address #9

@boxbeatsy

Description

@boxbeatsy

I just wanted to leave a note that we confirmed a fairly large memory leak associated with parse_address in our Heroku/Django application. Using heapy in a heroku bash shell, we deduced that the cities.csv file was continually being loaded and saved in memory. We didn't have the resources to find a workaround, so we moved to another package, but I wanted to file this ticket in case it flags the issue for anyone in the future who can save some time.

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