On Wed, 30 May 2012, Roy Stogner wrote: > While trying to track down a bug in my next ParallelMesh patch, I ran > into an apparent bug in our Parmetis support that dates back for I > don't know how far. > > We already serialize and fall back on Metis when we have more elements > than processors, and according to our code comments N_e<N_p is simply > an unsupported configuration for Parmetis... but I'm seeing crashes > (segfaults and/or double-frees) in quite a few other cases. Running > adaptivity_ex1 with 1 through 20 elements on 1 through 15 processors > gives failures whenever num_proc: num_elem is in > > 3:3 > 4:4 > 5:5,6,7,8 > 6:6,7,8 > 7:7,8,9 > 8:8,9,10,11 > 9:9,10,11,12 ...
Sadly, we seem to be getting the very same failure pattern with the current ParMETIS. --- Roy ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ Libmesh-devel mailing list Libmesh-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/libmesh-devel
