4 ms·
Right. Even in an entirely safe language you can have leaks, and valgrind is an effective way to find those leaks if you can afford the virtualisation overhead.
by tialaramex 5y ago
Right. Even in an entirely safe language you can have leaks, and valgrind is an effective way to find those leaks if you can afford the virtualisation overhead.
If you can't afford the virtualisation overhead, and you need to find leaks you should try what Raymond Chen suggests in "The poor man's way of identifying memory leaks" (not bothering to link since Microsoft will only move it anyway, they have several times since I read it). If you are too lazy to do it by hand, or find the technique works but wish it less manual, this is what Leakdice does:
https://github.com/tialaramex/leakdice https://github.com/tialaramex/leakdice
OR
https://github.com/tialaramex/leakdice-rust https://github.com/tialaramex/leakdice-rust
- unilynx 5y agohttp://bytepointer.com/resources/old_new_thing/20050815_224_the_poor_mans_way_of_identifying_memory_leaks.htm http://bytepointer.com/resources/old_new_thing/20050815_224_... (a site that tries to keep a proper backup of the ever moving writings of Chen)