Skip to content

Memory leak in long running process  #6

@scryclip

Description

@scryclip

I swapped out heapq.merge for this on a continuously running process. A new call to mulitmerge.merge would be made often it was passed a *list of generators with a key.
The instance of the multimerge.merge iterator would not be exhausted it would be used in a loop until a break and just be garbage collected and created anew in a future loop.
This would slowly leak memory. Switching back to heapq.merge resolved it.
Either something is not deleted In the C or the python gc is not able to fully clean up the multimerge instance when it removes it.

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