Skip to content

Ram Memory leak #105

@aishmurodov

Description

@aishmurodov

Hi!
I have a memory leak. According to the heap dump, the issue seems to be related to tracing, as a large number of listeners remain allocated. The case is not trivial, since load testing did not reveal any problems.

While reviewing your the code, I noticed res.on('finish', () => {}). As far as I understand, this handler is not triggered when the connection is terminated. Could it be that in case of a connection drop, the listeners are not properly cleaned up and therefore remain in memory?

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't working

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions