[Octave-bug-tracker] [bug #58790] Octave closes unexpectedly when memory allocation fails (Windows 32bit executable)

[Markus Mützel]

Follow-up Comment #24, bug #58790 (project octave):

I found only one way that can somewhat prevent us from being hit by memory
overcommit. That is to manually check the available memory (additionally to
checking whether "new" or "malloc" return a nullptr).
That would entail checking some of the fields that the new "memory" function
uses to gather its output.
Not sure whether this is costly though.

That still won't make sure that Octave won't ever be hit by the OOM killer.
But maybe we could prevent the OOM killer from triggering due to our own
actions.

    _______________________________________________________

Reply to this item at:

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

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