Skip to content

Memory leak on Node 19/20/22 with includeLocalVariables enabled #16041

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

Open
3 tasks done
tellisnz opened this issue Apr 14, 2025 · 3 comments
Open
3 tasks done

Memory leak on Node 19/20/22 with includeLocalVariables enabled #16041

tellisnz opened this issue Apr 14, 2025 · 3 comments
Labels

Comments

@tellisnz
Copy link

Is there an existing issue for this?

How do you use Sentry?

Sentry Saas (sentry.io)

Which SDK are you using?

@sentry/node

SDK Version

9.1.0

Framework Version

9.1.0

Link to Sentry event

No response

Reproduction Example/SDK Setup

See #14162

Our instance of issue is summarised in this comment

Ours is a reasonably high traffic express/node.js app, and with includeLocalVariables native memory usage increases until OOM.

Steps to Reproduce

See #14162

Expected Result

No native memory leak when using includeLocalVariables

Actual Result

Native memory leak is present when using includeLocalVariables

@getsantry getsantry bot moved this to Waiting for: Product Owner in GitHub Issues with 👀 3 Apr 14, 2025
@github-actions github-actions bot added the Package: node Issues related to the Sentry Node SDK label Apr 14, 2025
@Lms24
Copy link
Member

Lms24 commented Apr 14, 2025

Hey @tellisnz thanks for taking the time to report this!

I saw your comment in the other issue and I fully understand that this is not a priority for you. However, for us on our end, it's also hard to debug this without a reproduction or a memory profile.

I'll therefore add the Waiting for: Community label to this issue which will auto-close the issue unless someone replies with a reproduction.

EDIT: fixed comment link

@tellisnz
Copy link
Author

obviously not going to give a native memory dump.

I understand the difficulty in being able to figure this out without a reproduction, but the lack of effort in attempting to find it yourselves given clear evidence of an issue is surprising.

not sure why I was asked to create this if this was going to be the response.

@getsantry getsantry bot moved this from Waiting for: Community to Waiting for: Product Owner in GitHub Issues with 👀 3 Apr 14, 2025
@Lms24
Copy link
Member

Lms24 commented Apr 14, 2025

Again, I fully understand that this is frustrating, so I want to share some more context:

We already tried reproducing this in #14162 where the user originally even shared a reproduction attempt. Unfortunately, we could not reproduce it on our end. We asked for a memory profile or heap snapshot but did not receive one.

I will keep this open for now so that we can track it.

@stephanie-anderson stephanie-anderson removed the Package: node Issues related to the Sentry Node SDK label Apr 16, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
Status: No status
Development

No branches or pull requests

3 participants