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

Address memory consumption when Tracing is enabled **Cannot reproduce*** #3550

Open
jamescrosswell opened this issue Aug 22, 2024 · 2 comments

Comments

@jamescrosswell
Copy link
Collaborator

We've had multiple users report either memory leaks or high memory consumption when tracing is enabled in the SDK. Conversations with users exchanging logs etc. has not led to a successful resolution of the problems and none of the SDK maintainers has been able to reproduce a scenario that results in a memory leak.

We really need some way to be able to reproduce the problem to be able to investigate and find a solution.

Related Issues

@ericsampson
Copy link

Maybe Julian from the other issue would be willing to do some experimenting/data gathering, since it seems like they have a good repro situation…

@jamescrosswell
Copy link
Collaborator Author

Maybe Julian from the other issue would be willing to do some experimenting/data gathering, since it seems like they have a good repro situation…

cc: @Julian-Robinson @cliedeman

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: No status
Development

No branches or pull requests

3 participants