summaryrefslogtreecommitdiff
path: root/doc/emacs/trouble.texi
diff options
context:
space:
mode:
authorPo Lu <luangruo@yahoo.com>2022-04-08 19:36:03 +0800
committerPo Lu <luangruo@yahoo.com>2022-04-08 19:36:34 +0800
commit5c532fe30305393079674557256dbb96253fd517 (patch)
treefd4209fc8f2795e8787b37acfed0d6e7f33e4fd1 /doc/emacs/trouble.texi
parentdeb40b226764a0eb93a9fc2cafbbeeb9aeb31682 (diff)
downloademacs-5c532fe30305393079674557256dbb96253fd517.tar.gz
Recommend that the user turn off memory overcommit
* doc/emacs/trouble.texi (Memory Full): Tell the user that Emacs behaves best with overcommit off, and how to turn it off.
Diffstat (limited to 'doc/emacs/trouble.texi')
-rw-r--r--doc/emacs/trouble.texi14
1 files changed, 14 insertions, 0 deletions
diff --git a/doc/emacs/trouble.texi b/doc/emacs/trouble.texi
index 93f9c779dbf..f524a820220 100644
--- a/doc/emacs/trouble.texi
+++ b/doc/emacs/trouble.texi
@@ -296,6 +296,20 @@ editing in the same Emacs session.
out of memory, because the Buffer Menu needs a fair amount of memory
itself, and the reserve supply may not be enough.
+@cindex memory trouble, GNU/Linux
+ On GNU/Linux systems, the system does not normally report running
+out of memory to Emacs, and can instead randomly kill processes when
+they run out of memory. We recommend that you turn this behavior off,
+so that Emacs can respond correctly when it runs out of memory, by
+becoming the super user, editing the file @code{/etc/sysctl.conf} to
+contain the following lines, and then running the command @code{sysctl
+-p}:
+
+@example
+vm.overcommit_memory=2
+vm.overcommit_ratio=0
+@end example
+
@node Crashing
@subsection When Emacs Crashes