On Mon, Mar 22, 2021 at 1:39 PM Barry Smith <[email protected]> wrote:
> > Version of PETSc and MUMPS? We fixed a bug in MUMPs a couple years ago > that produced error messages as below. Please confirm you are using the > latest PETSc and MUMPS. > > You can run your production version with the option -malloc_debug ; > this will slow it down a bit but if there is memory corruption it may > detect it and indicate the problematic error. > > One also has to be careful about the size of the problem passed to > MUMPs since PETSc/MUMPs does not fully support using all 64 bit integers. > Is it only crashing for problems near 2 billion entries in the sparse > matrix? > "problems near 2 billion entries"? I don't understand. Should not be an issue if building petsc with 64-bit indices. > valgrind is the gold standard for detecting memory corruption. > > Barry > > > On Mar 22, 2021, at 12:56 PM, Chris Hewson <[email protected]> wrote: > > Hi All, > > I have been having a problem with MUMPS randomly crashing in our program > and causing the entire program to crash. I am compiling in -O2 optimization > mode and using --download-mumps etc. to compile PETSc. If I rerun the > program, 95%+ of the time I can't reproduce the error. It seems to be a > similar issue to this thread: > > https://lists.mcs.anl.gov/pipermail/petsc-users/2018-October/036372.html > > Similar to the resolution there I am going to try and increase icntl_14 > and see if that resolves the issue. Any other thoughts on this? > > Thanks, > > *Chris Hewson* > Senior Reservoir Simulation Engineer > ResFrac > +1.587.575.9792 > > >
