Run Valgrind on CI and fix memory leaks #2309
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Many gems with C-extensions have been using valgrind to check memory leaks, such as `prism`, `lrama`, and `json`. The simplest way to run valgrind on CI is through `ruby_memcheck` gem, which is used by both `prism` and `json`. So I followed its readme to add a new job `valgrind` to `ruby.yml`.
st0012
force-pushed
the
run-valgrind-on-ci
branch
from
9674479 to
686e0cc
Compare
Morriar
reviewed
Mar 7, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR:
prismandjsonand many other projects(Big thanks to @peterzhu2118 for helping on both the setup and fixing the issues 🙏 )