On Tue, Oct 21, 2014 at 9:01 AM, Rodrigo Broggi <rbrogg...@gmail.com> wrote: > The leak seems to be related to parallelization, I've run the program with > Valgrind and all "complains" derive from parallel statements both MPI and > openmp. Is there any advice on how to handle classes that contains implicit > MPI statements without causing problems... > > Here goes the heavy complain from Valgrind:
Sadly, this is pretty normal for most of the MPI stacks I've seen. You can't really fix these problems without patching your MPI implementation... none of the errors here are specifically libmesh-related AFAICT. You can investigate using valgrind suppressions so you at least don't see all this noise. Also, if you are having issues you should be compiling and running in debug mode. -- John ------------------------------------------------------------------------------ Comprehensive Server Monitoring with Site24x7. Monitor 10 servers for $9/Month. Get alerted through email, SMS, voice calls or mobile push notifications. Take corrective actions from your mobile device. http://p.sf.net/sfu/Zoho _______________________________________________ Libmesh-users mailing list Libmesh-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/libmesh-users
