Valgrind report vs. htop memory usage

  c++, memory-leaks, memory-profiling, valgrind

Recently I’ve encountered the problem that Valgrind report info did not match well (actually did not match at all) with the info that I literally dumped from htop memory usage. Is it even possible that Valgrind is smart enough to detect the leakage in the "worst" case? It occurs only on some set of input parameters of the program and this situation won’t reproduce in any other case (in other cases, memory usage would match pretty well).

Source: Windows Questions C++