getsentry / getsentry/sentry-javascript

Potential Memory Leak

Open
#19,663 9 comments 1 reaction 0 assignees View on GitHub
Bug Next.js
Dominant language
TypeScript
Stars
8.7k
Forks
1.8k
Avg merge
1d 17h
Merged PRs (30d)
515

Description

### Is there an existing issue for this?

- [x] I have checked for existing issues https://github.com/getsentry/sentry-javascript/issues
- [x] I have reviewed the documentation https://docs.sentry.io/
- [x] 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/nextjs

### SDK Version

10.22.0

### Framework Version

_No response_

### Link to Sentry event

_No response_

### Reproduction Example/SDK Setup

_No response_

### Steps to Reproduce

Have someone reporting a memory leak after enabling the SDK. They are seeing memory usage continue to climb on startup and while the application is running.

### Expected Result

Memory usage should not be climbing this way.

### Actual Result

Memory usage slowly climbs when Sentry is enabled.

### Additional Context

Adding details in linear.

### Priority

React with 👍 to help prioritize this issue. Please use comments to provide useful context, avoiding `+1` or `me too`, to help us triage it.

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.