|
From: | Markus Mützel |
Subject: | [Octave-bug-tracker] [bug #58790] Octave closes unexpectedly when memory allocation fails (Windows 32bit executable) |
Date: | Mon, 21 Sep 2020 06:59:04 -0400 (EDT) |
User-agent: | Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/85.0.4183.102 Safari/537.36 Edg/85.0.564.51 |
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/
[Prev in Thread] | Current Thread | [Next in Thread] |