|
From: | John W. Eaton |
Subject: | Re: Memory leaks in Octave |
Date: | Wed, 20 Sep 2017 18:11:03 -0400 |
User-agent: | Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.2.1 |
On 09/19/2017 01:05 PM, Rik wrote:
I didn't see this because I usually run with ASAN_OPTIONS set to "leak_check_at_exit=0:verbose=1". But, clearly this is a good reason to occasionally run the full Address Sanitizer which would detect slow memory leaks like this.
With this changeset http://hg.savannah.gnu.org/hgweb/octave/rev/5bf2e2ceace2I'm back down to 180k of indirect leaks and no direct leaks when starting octave-cli and immediately exiting. Most (or maybe all) appear to be from classdef initialization, so I'll see if I can do something about them as well.
jwe
[Prev in Thread] | Current Thread | [Next in Thread] |