[Octave-bug-tracker] [bug #58381] Consistent crash on large memory operations

[Mike Miller]

Update of bug #58381 (project octave):

                  Status:               Need Info => Wont Fix               

    _______________________________________________________

Follow-up Comment #4:

IMHO, it's best to use standard Unix resource limits to handle this kind of
problem.

I have the following in my octaverc


status = system (sprintf ("prlimit --pid %d --as=8589934592", getpid ()));


so that Octave always runs with a 8 GiB memory space. With this setting, I get
the following with your example


>> s = sortrows(vvec(mat));
error: out of memory or dimension too large for Octave's index type


But if the other maintainers think it's worth doing something more to try to
detect possible memory problems before they happen, ok.

    _______________________________________________________

Reply to this item at:

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

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