[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Octave-bug-tracker] [bug #57182] [octave forge] (signal) decimate cause
|
From: |
Mike Miller |
|
Subject: |
[Octave-bug-tracker] [bug #57182] [octave forge] (signal) decimate causes octave to be killed |
|
Date: |
Wed, 6 Nov 2019 19:45:18 -0500 (EST) |
|
User-agent: |
Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/78.0.3904.87 Safari/537.36 |
Follow-up Comment #4, bug #57182 (project octave):
Thanks. Octave does not send itself SIGKILL, so the kernel or another system
process is more likely.
Assuming this is a true Linux kernel running on the chromebook, I would
suspect the 'oom_kill_process' function. Look in the kernel logs for "out of
memory" or "oom killer". Given that Octave is receiving SIGKILL on one
particular system that may not have swap, and only when working with GB of
data, the Linux oom killer looks like a very likely cause.
_______________________________________________________
Reply to this item at:
<https://savannah.gnu.org/bugs/?57182>
_______________________________________________
Message sent via Savannah
https://savannah.gnu.org/