Skip to content

memory leak? #475

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.

Sign up for GitHub

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

Jump to bottom
Closed
lattice0 opened this issue Aug 6, 2022 · 2 comments
Closed

memory leak? #475

lattice0 opened this issue Aug 6, 2022 · 2 comments

Comments

@lattice0
Copy link

lattice0 commented Aug 6, 2022

We do valgrind checks on this repo and we're getting this: fzyzcjy/flutter_rust_bridge#582 (comment)

which only happens when we use this backtrace lib. Is it possible that this lib has a memory leak? Has it ever been tested with valgrind?

Thank you very much!
@bjorn3
Copy link
Member

bjorn3 commented Aug 6, 2022

I believe valgrind gives false positives on statx calls.

@workingjubilee
Copy link
Member

Closing for the same reasons rust-lang/rust#68979 was closed, this is kinda-sorta a Valgrind bug.

@workingjubilee workingjubilee closed this as not planned Won't fix, can't repro, duplicate, stale Jun 22, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@lattice0 @bjorn3 @workingjubilee