grpc-js memory leak

[tringuyencitigo]

Is there an existing issue for this?

• I have searched the existing issues

Current behavior

A lot of GRPC sessions are retained and are not garbage collected after responding to clients, as shown in the image.

Something related to channelz I suppose. It looks like I'm getting the same issue as in grpc/grpc-node#2068. I have upgraded to the latest version of grpc-js and it's still not working.

Minimum reproduction code

https://gist.github.com/tringuyencitigo/64a08c5790162483d98e2f638bfaaad9

Steps to reproduce

No response

Expected behavior

Memory consumption not gradually going up.

Package

• I don't know. Or some 3rd-party package
• @nestjs/common
• @nestjs/core
• @nestjs/microservices
• @nestjs/platform-express
• @nestjs/platform-fastify
• @nestjs/platform-socket.io
• @nestjs/platform-ws
• @nestjs/testing
• @nestjs/websockets
• Other (see below)

Other package

@grpc/grpc-js 1.7.1

NestJS version

@nestjs/microservices 9.1.2

Packages versions

Node.js version

14.17.0

In which operating systems have you tested?

• macOS
• Windows
• Linux

Other

I'm happy to provide anything required.

[kamilmysliwiec]

Please provide a minimum reproduction repository (Git repository/StackBlitz/CodeSandbox project).

[boolka]

Have the same here

[jmcdo29]

@boolka
Please provide a minimum reproduction repository (Git repository/StackBlitz/CodeSandbox project).

why reproductions are required

[chinmayacharya19]

Was there any resolution to this? it seems it was just closed without comments, Looks like user had provided code to reproduce.

We are noticing this in our staging environment, where health calls are constantly running, just starting the service and keeping it idle seems to have created a memory leak situation, the RAM is slowly piling up.

[fmonpelat]

I have the same issue, i have an app on k8s and when healthchecks are checked (through http with terminus and hybrid microservice), server gets memory leak so that at some point k8s is restarting the pod, we sticked with an old version previous to nestjs v8 (thats when it was switched to grpc-js).

[fmonpelat]

could this issue be reopened? @kamilmysliwiec ? now it has the code to reproduce.

[kamilmysliwiec]

There's still no minimum reproduction repository in this issue.

Please, create a new issue with a reproduction repository (that proves the memory leak really occurs of course).