Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Growing memory over time / Memory Leak #91

Open
axotion opened this issue Aug 26, 2024 · 2 comments
Open

Growing memory over time / Memory Leak #91

axotion opened this issue Aug 26, 2024 · 2 comments

Comments

@axotion
Copy link

axotion commented Aug 26, 2024

Hi,

I've been encountering a weird behaviour on k8s with some nodejs apps and pyroscope, as over the time, memory is growing indefinitely.

I've tried different docker image base OS (Alpine with node 18, node:20-bullseye-slim), setting pods replicas on k8s to 1, but without a luck.

Installed Pyroscope version

"@pyroscope/nodejs": "^0.3.11",

Usage in code

Screenshot 2024-08-26 at 11 47 35

Memory usage over time

Screenshot 2024-08-26 at 11 46 24 Screenshot 2024-08-26 at 11 53 02

As it's getting more strange, the pyroscope itself does not seem any memory growth

Self

Screenshot 2024-08-26 at 11 53 37 Screenshot 2024-08-26 at 11 53 56

Total

Screenshot 2024-08-26 at 11 55 43 Screenshot 2024-08-26 at 11 55 57
@nwalters512
Copy link
Contributor

FWIW, I reported something very similar in #28. I never got a resolution.

@axotion
Copy link
Author

axotion commented Aug 28, 2024

FWIW, I reported something very similar in #28. I never got a resolution.

Yea I saw it, but IIRC the issue you raise was on the version when this package was still using google pprof. They switched to datadog pprof.

And that surprised me. This package is basically a wrapper for datadog pprof, and I've been using datadog profiler in nodejs environment for years and tbh - never had such a problems

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants
@nwalters512 @axotion and others