Re:MTuner: C/C++ memory profiler and memory leak finder
by forrestthewoods on Sunday June 25, 2023 @05:46PM
(#36472940)
MTuner is a stellar tool. It doesn't require modifying or re-compiling your program. Once upon a time I had a subtle memory leak and it took less than 5 minutes from downloading to know exactly what was causing my leak and how to fix it. A++ great tool.
Re:MTuner: C/C++ memory profiler and memory leak finder
by forrestthewoods on Sunday June 25, 2023 @06:45PM
(#36473437)
Valgrind and Heaptrack don't support Windows. MTuner doesn't support Linux.
I'm not sure how the feature set compares MTuner. It looks like MTuner has a much richer and robust GUI for exploring the data. I'm not sure if it's intrinsically more capable. But it's certainly more user friendly and accessible!
Re:MTuner: C/C++ memory profiler and memory leak finder
by GuB-42 on Sunday June 25, 2023 @07:52PM
(#36473918)
In addition, Valgrind is based on a VM and is very slow (a 10x slowdown is typical). MTuner is based on code injection and is presumably much faster.
Valgrind approach has the advantage of being very reliable, flexible, and able to run software unmodified. It has many tools (sanitizers, profilers, ...) and they are all best in class. They typically don't offer GUIs but there are external visualizers. It biggest disadvantage, besides not supporting Windows is that it is awfully slow, so much that it is generally unacceptable for user acceptance testing, let alone production, and sometimes, it is effectively not usable at all.
If it is like other memory debuggers I have used (ex: dmalloc), it is fast enough for normal use, but not as exhaustive, and sometimes a bit finnicky.
Re:MTuner: C/C++ memory profiler and memory leak finder
by p0w3n3d on Monday June 26, 2023 @02:12AM
(#36476301)
Does it work on MacOS? I assume not, because Valgrind does not. It seems that MacOS has special memory management, which hides it from "host" programs that run subprocesses... Only "leaks" exist
Edit: some links: https://milostosic.github.io/MTuner/overview/why/ https://milostosic.github.io/MTuner/overview/how/
I'm not sure how the feature set compares MTuner. It looks like MTuner has a much richer and robust GUI for exploring the data. I'm not sure if it's intrinsically more capable. But it's certainly more user friendly and accessible!
Valgrind approach has the advantage of being very reliable, flexible, and able to run software unmodified. It has many tools (sanitizers, profilers, ...) and they are all best in class. They typically don't offer GUIs but there are external visualizers. It biggest disadvantage, besides not supporting Windows is that it is awfully slow, so much that it is generally unacceptable for user acceptance testing, let alone production, and sometimes, it is effectively not usable at all.
If it is like other memory debuggers I have used (ex: dmalloc), it is fast enough for normal use, but not as exhaustive, and sometimes a bit finnicky.
well don't forget macOS. definitely needs more contributors :D