-
-
Notifications
You must be signed in to change notification settings - Fork 1.8k
@sentry/ember leaks memory in tests #7258
Copy link
Copy link
Closed as not planned
Labels
Package: emberIssues related to the Sentry Ember SDKIssues related to the Sentry Ember SDK
Description
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? If you use the CDN bundles, please specify the exact bundle (e.g. bundle.tracing.min.js) in your SDK setup.
@sentry/ember
SDK Version
7.38.0
Framework Version
4.10.0
Link to Sentry event
No response
SDK Setup
Sentry.init({
enabled: environment === 'production',
dsn,
environment,
integrations: [new BrowserTracing()],
tracesSampleRate: 0.01,
release: `a string`,
});Steps to Reproduce
run a series of acceptance tests, take a heap snapshot once tests are completed, examine retainers. You may want to use https://github.com/dnachev/heapdump-cleanup to cleanup WeakMap retainers to get a clear view.
Expected Result
No retained app instances.
Actual Result
Retained App instance per-acceptance-test due to instrumentation.
I was able to resolve this for now by removing performance instrumentation (we were barely using it even in prod). Others hitting this will want to ensure that at least the following is true in test and development environments in config/environment.js
ENV = {
'@sentry/ember': {
disablePerformance: true,
},
}Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
Package: emberIssues related to the Sentry Ember SDKIssues related to the Sentry Ember SDK
Fields
Give feedbackNo fields configured for issues without a type.

