|
From: | John W. Eaton |
Subject: | [Octave-bug-tracker] [bug #47372] Memory leaks and segmentation faults in Octave |
Date: | Wed, 06 Apr 2016 21:18:12 +0000 |
User-agent: | Mozilla/5.0 (X11; Linux x86_64; rv:44.0) Gecko/20100101 Firefox/44.0 Iceweasel/44.0 |
Follow-up Comment #98, bug #47372 (project octave): I noticed that there was no call to terminate the JVM on exit, at least that I could see. It looks like the function __java_exit__ is supposed to allow one to do that from the Octave command line. So I did a comparison of test ov-java.cc quit and test ov-java.cc __java_exit__ quit And I see SUMMARY: AddressSanitizer: 169705 byte(s) leaked in 60 allocation(s). for the case *without* __java_exit__ and SUMMARY: AddressSanitizer: 177464 byte(s) leaked in 82 allocation(s). for the case *with* it. WTF? _______________________________________________________ Reply to this item at: <http://savannah.gnu.org/bugs/?47372> _______________________________________________ Message sent via/by Savannah http://savannah.gnu.org/
[Prev in Thread] | Current Thread | [Next in Thread] |