[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Octave-patch-tracker] [patch #9924] Suggestion for a memory() function

From: Lars Kindermann
Subject: [Octave-patch-tracker] [patch #9924] Suggestion for a memory() function
Date: Sat, 23 May 2020 16:05:41 -0400 (EDT)
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Firefox/68.0

Follow-up Comment #23, patch #9924 (project octave):

I continued to work on the linux code and while testing I realized there is a
severe problem in providing the matlab-compatible function.

After allocating all of the memory the MemAvailableAllArrays or
MaxPossibleArrayBytes fields suggest, the system will be most probably dead. 

After executing

[usr, sys] = memory;

my system went (as expectd) into heavy swapping, but because really all memory
was used up, it became totally inaccessible. All attemps to kill octave
failed. And because the memory usage was still legit in theory, the OOM killer
did not step in. After two hours I forcefully powered down the system under
heavy disk load - with the result that the partition table was destroyed and I
lost my data.
We should at least place some warning into the documentation about this... 


Reply to this item at:


  Message sent via Savannah

reply via email to

[Prev in Thread] Current Thread [Next in Thread]