valgrind and openmp, still reachable and possibly lost, is that bad?

Question

c++ newbie here.

I\'ve been improving my memory management skills over the last few days, and my program no longer leaks memory according to valgrind. In fact, I get

Answer 1

Still reachable is not a memory leak.

Still reachable means that a block of memory has not been freed but there are still valid pointers to the start of that block in registers or memory that has not been freed.

You need to have a look at the Valgrind FAQ. The actual reason for libgomp causing the warning is explained here.