[Octave-bug-tracker] [bug #63803] Saving causes OOM, crash, and loss of already saved data

[Rik]

Follow-up Comment #2, bug #63803 (project octave):

My guess is that the other variables have nothing to do with it and it is
'arr' which is the problem.  The only variable that was saved was 'adj', but
this is also the only variable that precedes 'arr' when listed alphabetically.
 My guess is that Octave has a for loop over the variables and it is in the
same order as displayed by 'whos'.

If this is correct, you could probably just test with the 'arr' and 'lst'
variables.  That might help narrow things down.

In one shell window I ran


while (1)
  free -h
  sleep 1
end


In another shell I ran octave as a CLI and then executed


y = false (1e5, 2e4);
y(1:3:end) = true;


This variable takes up 2 GB.  Then I tried saving with


save -binary test.mat y


Memory usage peaks at 4 GB during the save which would imply two copies of the
variable are made during the save process.



    _______________________________________________________

Reply to this item at:

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

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