octave-bug-tracker
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Octave-bug-tracker] [bug #31644] Memory leaks


From: anonymous
Subject: [Octave-bug-tracker] [bug #31644] Memory leaks
Date: Tue, 19 Apr 2011 19:51:23 +0000
User-agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.16) Gecko/20110323 Ubuntu/10.04 (lucid) Firefox/3.6.16

Follow-up Comment #5, bug #31644 (project octave):

I confirm these memory leaks for 3.2.4 (debian pkg), 3.4.0 and 3.5.0 (compiled
from sources with --enable-openmp). 
Simply starting octave without any toolboxes any closing it 
    valgrind octave-3.4.0 -f --eval "1;"
reports the memory leaks (see below). Surprisingly, no memory leaks are
reported with ./run-octave      
   valgrind ./run-octave -f --eval "1;"


Alois 



$valgrind octave-3.4.0 -f --eval "1;"
==22131== Memcheck, a memory error detector
==22131== Copyright (C) 2002-2010, and GNU GPL'd, by Julian Seward et al.
==22131== Using Valgrind-3.6.0.SVN-Debian and LibVEX; rerun with -h for
copyright info
==22131== Command: octave-3.4.0 -f --eval 1;
==22131== 
GNU Octave, version 3.4.0
Copyright (C) 2011 John W. Eaton and others.
This is free software; see the source code for copying conditions.
There is ABSOLUTELY NO WARRANTY; not even for MERCHANTABILITY or
FITNESS FOR A PARTICULAR PURPOSE.  For details, type `warranty'.

Octave was configured for "x86_64-unknown-linux-gnu".

Additional information about Octave is available at http://www.octave.org.

Please contribute if you find this software useful.
For more information, visit http://www.octave.org/help-wanted.html

Read http://www.octave.org/bugs.html to learn how to submit bug reports.

For information about changes from previous versions, type `news'.


==22131== 
==22131== HEAP SUMMARY:
==22131==     in use at exit: 3,053,530 bytes in 7,676 blocks
==22131==   total heap usage: 151,134 allocs, 143,458 frees, 18,998,786 bytes
allocated
==22131== 
==22131== LEAK SUMMARY:
==22131==    definitely lost: 524 bytes in 27 blocks
==22131==    indirectly lost: 4,676 bytes in 38 blocks
==22131==      possibly lost: 1,008,271 bytes in 2,229 blocks
==22131==    still reachable: 2,040,059 bytes in 5,382 blocks
==22131==         suppressed: 0 bytes in 0 blocks
==22131== Rerun with --leak-check=full to see details of leaked memory
==22131== 
==22131== For counts of detected and suppressed errors, rerun with: -v
==22131== ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 7 from 7)


    _______________________________________________________

Reply to this item at:

  <http://savannah.gnu.org/bugs/?31644>

_______________________________________________
  Message sent via/by Savannah
  http://savannah.gnu.org/




reply via email to

[Prev in Thread] Current Thread [Next in Thread]