|
From: | John W. Eaton |
Subject: | [Octave-bug-tracker] [bug #47372] Memory leaks and segmentation faults in Octave |
Date: | Fri, 08 Apr 2016 18:32:14 +0000 |
User-agent: | Mozilla/5.0 (X11; Linux x86_64; rv:44.0) Gecko/20100101 Firefox/44.0 Iceweasel/44.0 |
Follow-up Comment #110, bug #47372 (project octave): I think the biggest leak for the Java interface comes from loading octave.jar. It seems that when that is done, the JVM never releases the memory for it. I'm attaching a simple self-contained program that shows leaks for just loading the jvm shared library, creating a jvm and then destroying it and unloading the shared library. I think we should just give up on fixing any of these problems. (file #36868) _______________________________________________________ Additional Item Attachment: File name: java-mem.cc Size:1 KB _______________________________________________________ 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] |