Replies: 2 comments
-
oomkiller will kill processes using the most memory when it fills up, and not having swap means there is no other recourse, so probably yes |
Beta Was this translation helpful? Give feedback.
0 replies
-
Thank you for the confirmation! I'll enable swap and if I notice processes
dying less I'll report back to close the loop.
…On Tue, Nov 19, 2024, 11:14 PM Dan ***@***.***> wrote:
oomkiller will kill processes using the most memory when it fills up, and
not having swap means there is no other recourse, so probably yes
—
Reply to this email directly, view it on GitHub
<#2211 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAD6K6VGPDQVDVAUYN5NBWT2BQLDVAVCNFSM6AAAAABSDT7TPKVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTCMZRG44TIMY>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Does anyone have any experience with morbo/daemon/prefork processes just dying? I find this most common when they are running for a while, especially in a tmux or vscode ssh session and the shell goes away too! Moreover, I find this most common when the system is running very low on RAM. But why is the process just dying without any errors or warnings, how is it taking out the shell, and why -- oh, sorry, I was going to say why isn't the process rolling into swap? This system has no swap configured. Is that the explanation?
Beta Was this translation helpful? Give feedback.
All reactions