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

Heap dumps should be deleted once they've been captured #4009

Open
jamescrosswell opened this issue Feb 27, 2025 · 0 comments
Open

Heap dumps should be deleted once they've been captured #4009

jamescrosswell opened this issue Feb 27, 2025 · 0 comments

Comments

@jamescrosswell
Copy link
Collaborator

So yeah, we know where the dump file is and could just let people know the location where it's been stored, if it's too big to add as an attachment. I imagine a lot of folks wouldn't have access to it in a production environment though.

But if we're doing this now we need to keep track and delete old files etc to avoid a disk filling up.
If we're not sending to Sentry, I would delete the dump file and log diag logger error about it.

If Sentry increases the size limit one would need to bump the SDK (and we'd need to amend the SDK limits though)

Originally posted by @bruno-garcia in #4007

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

No branches or pull requests

1 participant