Valgrind claims invalid free when running icoFoam from OpenFOAM 1.6-ext
Dear Foamers
Checking the memory management of my own application I ran into an invalid free, which I could not find anywhere in my code. Turns out that valgrind complains about invalid free in solvers like icoFoam, here is the complete output: Code:
==4973== Invalid free() / delete / delete[] The same also seems to happen with other solver such as potentialFoam. This looks like a bug to me. |
I don't get this error, although I remember getting some like it before and it's something to do with glibc, maybe update that?
Looks identical to this: http://sourceware.org/bugzilla/show_bug.cgi?id=10610 |
This is all in POSIX.C with functions like
Foam::userName() (POSIX.C:123) getpwuid_r (in /lib/libc-2.9.so) getpwuid (in /lib/libc-2.9.so) and it is inconsequential. I have recently cleaned up bugs in HashTables as well, but it looks like this is at the level of OS interface and I cannot be bothered to chase it. If you clean up POSIX.C to do the deletes as needed I will pick up the code, merge it and buy you a beer! Deal? Hrv |
Is the invalid free not a separate error from the memory leak?
I also don't see how Foam::userName() (POSIX.C:123) is at fault, there's no dynamic memory allocation in there. |
All times are GMT -4. The time now is 03:32. |