Stefano Zampini <[email protected]> writes: > I noticed that recent versions of MKL produce memory leaks if the memory > management functions are not properly called at the end of the program. > > http://software.intel.com/en-us/node/438664 > > Do we need to add those calls in PetscFinalize or it is user responsibility?
Hmm, looks like the user could run with MKL_DISABLE_FAST_MM=1. Maybe we should call mkl_disable_fast_mm() when running in debug mode. I don't know if calling mkl_free_buffers has an impact on other running parts of a program (if the user is calling MKL independent of PETSc).
pgpH8UNIQTVx2.pgp
Description: PGP signature
