[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Octave-bug-tracker] [bug #40233] Memory leak in oct-shlib
From: |
Rik |
Subject: |
[Octave-bug-tracker] [bug #40233] Memory leak in oct-shlib |
Date: |
Fri, 11 Oct 2013 17:38:17 +0000 |
User-agent: |
Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:24.0) Gecko/20100101 Firefox/24.0 |
Follow-up Comment #2, bug #40233 (project octave):
I agree that this isn't a threat to the stability of Octave. However, I
wouldn't close the report because there is definitely something going on. The
example I listed lost only 56 bytes which is inconsequential. However over a
full run of the test suite, 4096 bytes were lost. Although the growth is very
slow, it doesn't appear that there is a cap.
Enough changes have taken place that the whole test suite needs to be re-run
under valgrind (and I know you are doing that from a different bug report).
Perhaps this has been fixed. If not, I would try running the test suite and
executing a 'clear -all' at the end to see if this is only valgrind not
recognizing objects that would be cleaned up in the course of normal events.
_______________________________________________________
Reply to this item at:
<http://savannah.gnu.org/bugs/?40233>
_______________________________________________
Message sent via/by Savannah
http://savannah.gnu.org/