Bug#863291: libscalapack-openmpi1: memory leak in pXgemr2d

2017-07-25 Thread Drew Parsons
On Tue, 25 Jul 2017 23:03:23 +0800 Drew Parsons wrote: > Hi Grigory, >  > scalapack 2.0 is now available in experimental. >  > Could you test if your pXgemr2d problem persists when built against > scalapack 2.0 with openmpi 2.1.1 ? Note that scalapack 2.0 incorporates blacs, so your compile line

Bug#863291: libscalapack-openmpi1: memory leak in pXgemr2d

2017-07-25 Thread Drew Parsons
Hi Grigory, scalapack 2.0 is now available in experimental. Could you test if your pXgemr2d problem persists when built against scalapack 2.0 with openmpi 2.1.1 ? Thanks, Drew

Bug#863291: libscalapack-openmpi1: memory leak in pXgemr2d

2017-05-25 Thread Grigory Kolesov
Dear Muammar, > It could be that the actual leak is in OpenMPI, but somehow it triggered > only by pXgemr2d. I apologize for blaming Scalapack/pXgemr2d, a little more investigation showed that the bug does seem to be in OpenMPI. In short, recompiling Scalapack doesn't help, recompiling/upgradi

Bug#863291: libscalapack-openmpi1: memory leak in pXgemr2d

2017-05-24 Thread Grigory Kolesov
Package: libscalapack-openmpi1 Version: 1.8.0-13 Severity: important Dear Maintainer, After upgrade to the latest Debian testing my code started leaking memory at horrendous pace. The valgrind output traced the leak to Cpdgemr2d and Cpzgemr2d (see below). It could be that the actual leak is in O