Fri 11 Oct 2013 05:38:17 PM UTC, comment #2:
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.
|
Thu 10 Oct 2013 08:57:43 PM UTC, comment #1:
I haven't investigated, but I suspect that this is another case of allocating resources and not explicitly cleaning them up before Octave exits.
If this is due to loading .oct files, then I'm only concerned about it if Octave is not properly freeing memory if you do something like repeatedly call a function defined in a .oct file, then clear it. If that causes Octave to grow without bound, then there is an actual leak we should worry about.
If I do
Octave does not appear to grow. I can verify with lsof that qr.oct is loaded when I call it and closed when I clear it.
So maybe we should close this report?
|
Thu 10 Oct 2013 03:47:31 AM UTC, original submission:
The leak is in the shared library code oct-shlib. Perhaps helpful, or perhaps a red herring, it is a PKG_ADD command that starts the leak sequence.
|