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

How to test for memory leaks #22

Open

bzf opened this issue Apr 24, 2020 · 0 comments

Owner

bzf commented Apr 24, 2020

Could we run valgrind in a Github Action and read some files from an archive and see if something got leaked?

The text was updated successfully, but these errors were encountered:

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment