Run Valgrind on CI to Detect Memory Leaks #3533
Labels
build-system
The Wasmer repo's build and CI system
🎉 enhancement
New feature!
memory-leak
priority-low
Low priority issue
🏚 stale
Inactive issues or PR
To prevent a situation like #3485 from re-occurring we should include a Valgrind job on CI that runs a bunch of tests in a typical usage scenario, and fails in case of leaks.
We do have oss-fuzz integration now, but we should still detect these things early on in our own tooling.
The text was updated successfully, but these errors were encountered: