Closed pyamsoft closed 9 years ago
After trying to build both with g++ and clang++, the same memory leak still occurs. I believe this to be an issue with valgrind itself then.
Building on Valgrind under Ubuntu 14.04 yielded no memory leak. This is a Valgrind issue and shall be closed as such.
As of version 1.1.15, a memory leak has been noticed. After careful testing, I have come to the assumption that the leak is not directly associated with pstate-frequency.
A small test was conducted in which a Hello World program was built using g++ 5.1, and then checked with the valgrind-3.10 program. A memory leak of 72,704 bytes in 1 block was found. This same leak exists in pstate-frequency when run against valgrind. I have made the assumption that the leak is either in g++ or valgrind itself, and therefore will not be attempting to bisect and find a memory leak as I assume one does not technically exist.