Re: [Libmesh-users] Memory leak detected

2016-11-30 Thread John Peterson
On Wed, Nov 30, 2016 at 3:50 PM, Harshad Sahasrabudhe wrote: > Hi all, > > The libmesh reference counter shows that there are fewer destructions that > creations. Is there any easy way to find out which objects in my code are > not destroyed? > You leaked ~140,000 Elems, I'd start by searching y

Re: [Libmesh-users] Memory leak detected

2016-11-30 Thread David Knezevic
On Thu, Dec 1, 2016 at 6:50 AM, Harshad Sahasrabudhe wrote: > Hi all, > > The libmesh reference counter shows that there are fewer destructions that > creations. Is there any easy way to find out which objects in my code are > not destroyed? > > Thanks, > Harshad > The reference count info shou

[Libmesh-users] Memory leak detected

2016-11-30 Thread Harshad Sahasrabudhe
Hi all, The libmesh reference counter shows that there are fewer destructions that creations. Is there any easy way to find out which objects in my code are not destroyed? Thanks, Harshad | Reference count information