Potential Memory Leak

[tbadlov]

Thanks for stopping by to let us know something could be better!

PLEASE READ: If you have a support contract with Google, please create an issue in the support console instead of filing on GitHub. This will ensure a timely response.

Please run down the following list and make sure you've tried the usual "quick fixes":

• Search the issues already opened: https://github.com/googleapis/cloud-debug-nodejs/issues
• Search the issues on our "catch-all" repository: https://github.com/googleapis/google-cloud-node
• Search StackOverflow: http://stackoverflow.com/questions/tagged/google-cloud-platform+node.js

If you are still having issues, please be sure to include as much information as possible:

Environment details

• OS: Google App Engine
• Node.js version: 12.14.x
• npm version: 6.13
• @google-cloud/debug-agent version: 4.2.1

Steps to reproduce

We found that the package cause a memory leak. This image shows our application memory with the package and without it.

We are running on Google App Engine with 4 nodes. Any help is appreciated.

Thanks!

[DominicKramer]

It looks like the issue node #28420 is impacting the version of node you are using. I suspect it could be the root cause.

[legopin]

@DominicKramer node version upgrade didn't resolve the issue.

We are observing a similar issue on the upgraded node version.
The memory usage gradually climbs until OOM kill when debug agent is enabled. After it was disabled the memory usage is stable.

Running on GKE (Google Kubernetes Engine) pod

• OS: official node docker image
• Node.js version:12.16.0
• npm version:6.13.4
• @google-cloud/debug-agent version:4.2.2

[DominicKramer]

Thank you for the update. Have you seen similar problems on GCP services other than GKE?

[legopin]

That's the only GCP service we use. We have all our services running under kubernetes

[tbadlov]

Ours is on AppEngine

[DominicKramer]

@legopin and @tbadlov thanks for the update.

[soldair]

if anyone has a repro gist or repository we can run that leaks this way that would help us get to the bottom off this a little more quickly. It helps to confirm that we're solving the problem you're hitting.