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

[tellisnz]

Is there an existing issue for this?

• I have checked for existing issues https://github.com/getsentry/sentry-javascript/issues
• I have reviewed the documentation https://docs.sentry.io/
• I am using the latest SDK release https://github.com/getsentry/sentry-javascript/releases

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

[Lms24]

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]

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.

[Lms24]

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.