#838 memory leak in parallel yaspgrid communicator
Metadata
| Property | Value |
|---|---|
| Reported by | Nagaiah (nagaiah.chamakuri@gmail.com) |
| Reported at | Nov 4, 2010 12:07 |
| Type | Bug Report |
| Version | Git (pre2.4) [autotools] |
| Operating System | Unspecified / All |
| Last edited by | Christian Engwer (christi@conan.iwr.uni-heidelberg.de) |
| Last edited at | Nov 15, 2010 18:58 |
| Closed by | Christian Engwer (christi@conan.iwr.uni-heidelberg.de) |
| Closed at | Nov 15, 2010 18:58 |
| Closed in version | Unknown |
| Resolution | Fixed |
| Comment | in dune-grid rev. 7089 |
Description
It seems there is a memory leak in yaspgrid communicator. For test case, I am running the "nonlineardiffusion.cc" code in pdelab-howto. This happens only when number of processors are 4 or more. there is no memory leak if it runs sequentially or less than 4 processors. The valgrind output log file is attached. I am using the following command to produce that output file. Tested with current SVN version.
mpiexec -np 4 /usr/bin/valgrind --leak-check=full --trace-children=yes --log-file=output.txt ./nonlineardiffusion 1
It seems the source of bug triggers at line number 3043 in yaspgrid.hh, but I am not sure.