Skip to content

valgrind complains about memory leackage in simpleFoam when running in parallel

I am trying to hunt down a memory leakage problem within an in-house class that appears when running in parallel but not in serial.

In the process of doing so, I discovered mpirunDebug (there seems to be a nice script for everything you need :) )

When executing it however, valgrind reports multiple leakage errors related to UPstream.

I then switched to the pitchDaily case ran with simpleFoam and I get similar errors (case attached case pitzDaily.tar.gz)

I have tested in the following environments

  • OpenFOAM version: v2206
  • OS: CentOS Linux release 7.5.1804
  • Compiler: gcc (OpenFOAM) 9.3.0
  • valgrind: valgrind-3.13.0
  • mpi: OpenMPI 1.10.7

Log file from processor0: processor0_env1.log

  • OpenFOAM version: v2206 (binary pack)
  • OS: Ubuntu 22.04
  • Compiler: gcc (Ubuntu 11.2.0-19ubuntu1) 11.2.0
  • valgrind: valgrind-3.18.1
  • mpi: OpenMPI 4.1.2

Log file from processor0: processor0_env2.log

As you will see, some errors are common, some exist only in the first environment but all seem to be related to UPStream somehow.

I am assuming these are false positives from valgrind. Any idea what is causing them or how they can be suppressed? They tend to pollute the outcome to a degree that makes tracking the real issue (if any) quite challenging.

Any help is appreciated.