aboutsummaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorEli Zaretskii2022-04-09 12:57:08 +0300
committerEli Zaretskii2022-04-09 12:57:08 +0300
commitd327fd594da7d7207c2d47414a6c47ff0c0e2598 (patch)
treef0c9390aba4313b642fe829f7525de1afe22c745
parentf3f20a37fb3b7e02fc52b3787968e2a332f52119 (diff)
downloademacs-d327fd594da7d7207c2d47414a6c47ff0c0e2598.tar.gz
emacs-d327fd594da7d7207c2d47414a6c47ff0c0e2598.zip
; * doc/emacs/trouble.texi (Memory Full): Minor copyedits.
-rw-r--r--doc/emacs/trouble.texi27
1 files changed, 19 insertions, 8 deletions
diff --git a/doc/emacs/trouble.texi b/doc/emacs/trouble.texi
index f524a820220..8da96de1cb4 100644
--- a/doc/emacs/trouble.texi
+++ b/doc/emacs/trouble.texi
@@ -296,20 +296,31 @@ editing in the same Emacs session.
296out of memory, because the Buffer Menu needs a fair amount of memory 296out of memory, because the Buffer Menu needs a fair amount of memory
297itself, and the reserve supply may not be enough. 297itself, and the reserve supply may not be enough.
298 298
299@cindex memory trouble, GNU/Linux 299@cindex out of memory killer, GNU/Linux
300 On GNU/Linux systems, the system does not normally report running 300@cindex OOM killer
301out of memory to Emacs, and can instead randomly kill processes when 301 On GNU/Linux systems, Emacs does not normally get notified about
302they run out of memory. We recommend that you turn this behavior off, 302out-of-memory situations; instead, the OS can kill the Emacs process
303so that Emacs can respond correctly when it runs out of memory, by 303when it runs out of memory. This feature is known as the
304becoming the super user, editing the file @code{/etc/sysctl.conf} to 304@dfn{out-of-memory killer}, or @dfn{@acronym{OOM} killer}. When this
305contain the following lines, and then running the command @code{sysctl 305behavior is in effect, Emacs is unable to detect the out-of-memory
306-p}: 306situation in time, and won't be able to let you save your buffer as
307described above. However, it is possible to turn off this behavior of
308the OS, and thus allow Emacs a chance to handle the out-of-memory
309situation in a more useful manner, before it is killed. To do that,
310become the super user, edit the file @code{/etc/sysctl.conf} to
311contain the lines shown below, and then invoke the command
312@w{@kbd{sysctl -p}} from the shell prompt:
307 313
308@example 314@example
309vm.overcommit_memory=2 315vm.overcommit_memory=2
310vm.overcommit_ratio=0 316vm.overcommit_ratio=0
311@end example 317@end example
312 318
319@noindent
320Please note that the above setting affects all the processes on the
321system, and in general the behavior of the system under memory
322pressure, not just the Emacs process alone.
323
313@node Crashing 324@node Crashing
314@subsection When Emacs Crashes 325@subsection When Emacs Crashes
315 326