[Octave-bug-tracker] [bug #60979] Memory space used per GNU octave increases inexplicably

[anonymous]

Follow-up Comment #3, bug #60979 (project octave):

Unable to reproduce a memory leak on Linux with both tests. Might be
Windows-specific alone?

@OP (Simon), some questions for you:

1. Your Octave versions are listed as "6.0.1 and 6.0.3". Should that be 6.1.0
and 6.3.0 or did you find these versions from a non-release location
somewhere?

2. How much RAM do you have and how many GB had Octave used up at the freezing
point? How many hours does that take? If we can get an estimate of how many MB
per hour are leaking at your end (and we haven't found a leak yet), we can
wait an appropriately scaled time if we have a different amount of RAM to see
the leak.

3. This hack may help you in general, which I learned from my Matlab-using
days on Windows. If you create a suitably large array like perms(1:10) or
perms(1:11), and then clear it, you'll find that a lot more memory becomes
available to Octave (or Matlab for that matter). It's something to do with
Windows caching a lot of memory for programs that have been running for a long
time, and sometimes that needs to be flushed by allocating and deallocating a
big chunk of memory. Let us know if this works for you.

    _______________________________________________________

Reply to this item at:

  <https://savannah.gnu.org/bugs/?60979>

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