[Octave-bug-tracker] [bug #53943] memory usage explodes on a javaMethod call

[Mike Miller]

Update of bug #53943 (project octave):

                Severity:              3 - Normal => 2 - Minor              
                  Status:                    None => Works For Me           

    _______________________________________________________

Follow-up Comment #1:

This looks to me like the expected behavior of Java, the amount of memory that
Java uses is outside of Octave's control.

FWIW I see the following numbers on my system.

* octave-cli --norc uses about 650 MiB
* octave --norc uses about 1,322 MiB
* a standalone C program that creates a Java VM uses about 6,584 MiB
* octave-cli --norc after loading a Java VM uses about 8,387 MiB
* octave --norc after loading a Java VM uses about 9.037 MiB

The baseline memory difference between octave-cli and octave-gui is about 650
MiB. This is the same before and after Java is loaded.

The memory difference on my system due to starting a Java VM in Octave is
about 7,730 MiB. This is slightly larger than the memory used by a simple C
program that just creates a Java VM, but not much different.

So on my system I see a large increase of about 7.7 GiB when Octave creates a
Java VM, but not the 34 GiB increase that you are seeing. This may be due to
system configuration differences or a different version or build of Java.

You might try measuring the memory usage of a simple Java hello world program.
On my system with the same version of Java, I see a memory usage of about 6.7
GiB, which is consistent with the other examples I tested.

    _______________________________________________________

Reply to this item at:

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

_______________________________________________
  Message sent via Savannah
  https://savannah.gnu.org/