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

Memory leak when migrate signalfx to splunk/otel library #752

Open
blacktrue opened this issue Jul 6, 2023 · 3 comments
Open

Memory leak when migrate signalfx to splunk/otel library #752

blacktrue opened this issue Jul 6, 2023 · 3 comments

Comments

@blacktrue
Copy link

Hi

I have a memory leak when migrate signalfx library to splunk/otel, I have confirmed with other services that they migrate and have the same behavior.

Captura de pantalla 2023-07-05 a la(s) 19 14 42

My implementation is:

package.json

"scripts": {
  "prod": "APP_ENV=production node --max_old_space_size=4096 -r @splunk/otel/instrument src/app.js"
}

app.js

/* eslint-enable global-require */
const { startProfiling } = require('@splunk/otel');
startProfiling({
  serviceName: process.env.SPLUNK_SERVICE_NAME,
})

Any idea what is happening?

@seemk
Copy link
Contributor

seemk commented Dec 14, 2023

Is this only with CPU profiling? Or was memory profiling enabled as well?

@blacktrue
Copy link
Author

@seemk both profiling

@seemk
Copy link
Contributor

seemk commented Mar 28, 2024

@blacktrue Which version are you using? Can you upgrade to the latest version?

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

2 participants