Re: Memory Leaks with Trilinos

Hi Trevor, My mystery deepens. Today, I've compiled and tried the following combinations of Trilinos/Swig: 12.8.1/3.0.2 11.14.3/3.0.2 11.12.1/3.0.2 11.10.1/2.0.8 11.2.5/2.0.8 All of these combinations leak memory at about the same rate. I am using Boost 1.54, Openmpi 1.6.5, and GCC

RE: Memory Leakage & Object Build-up with FiPy Sweeps

Dear Jonathan, Daniel, Thank you for your responses. Just yesterday, I discovered and solved this problem (another remains). It wasn't a result of calls to .sweep. The time-varying boundary condition for one of the PDEs was being re-defined within the time-stepping loop using the

Re: Memory Leakage & Object Build-up with FiPy Sweeps

Hi all, Could Ian's issue be related to the issues I came across at the end of March? Trevor Keller seems to have isolated my memory leak to versions of Trilinos newer than 12.0. Trevor, It seems that I never got around to testing an older version of Trilinos, I'll do that now. -Mike On

Re: Memory Leakage & Object Build-up with FiPy Sweeps

I have access to their code. Ian, please provide an explicit recipe for demonstrating the leak with the code in your github repo. - Jon > On Oct 11, 2016, at 11:15 AM, Daniel Wheeler > wrote: > > Hi Ian, > > Could you possible post your code or a version of the

Re: Memory Leakage & Object Build-up with FiPy Sweeps

Hi Ian, Could you possible post your code or a version of the code that demonstrates the problem? Also, do you have the same issue with different solver suites? Cheers, Daniel On Fri, Sep 30, 2016 at 12:41 PM, Campbell, Ian wrote: > Hi All, > > > > We are