all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: npostavs@users.sourceforge.net
To: Ricardo Wurmus <rekado@elephly.net>
Cc: 27498@debbugs.gnu.org
Subject: bug#27498: 25.2; Memory leak in M-x shell
Date: Mon, 26 Jun 2017 08:01:14 -0400	[thread overview]
Message-ID: <87k23znek5.fsf@users.sourceforge.net> (raw)
In-Reply-To: <87lgofko1i.fsf@elephly.net> (Ricardo Wurmus's message of "Mon, 26 Jun 2017 13:04:41 +0200")

forcemerge 26952 27498
quit

Ricardo Wurmus <rekado@elephly.net> writes:

> Emacs leaks memory as lines are printed in a shell buffer.  Here is a
> recipe:
>
>     emacs -Q
>     M-x shell
>     yes "This should not leak, but it does."
>
> Observe the memory usage grow in a tool like “top”.  Once you decide
> that Emacs has eaten enough memory, kill the shell buffer.  Note that
> memory is not released.
>
> This is a problem for me because I often compile software in shell
> buffers (via “guix build”).  The compilation processes often print out
> very large amounts of text and Emacs quickly eats up all memory on my
> machine, freezing it.  I can only recover from this by killing Emacs
> (which is terrible, because I live in Emacs).

This is Bug#26952, it's due to using the custom "GNU version of malloc"
without the "relocating allocater" (there were several bugs with the
relocating allocater in 25.1).  To fix you can configure with
REL_ALLOC=yes (this should be okay in 25.2), or use Emacs' master branch
where the standard system allocater can be used once again.





  reply	other threads:[~2017-06-26 12:01 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-26 11:04 bug#27498: 25.2; Memory leak in M-x shell Ricardo Wurmus
2017-06-26 12:01 ` npostavs [this message]
2017-06-26 13:14   ` Ricardo Wurmus
2017-06-27  5:17   ` Ricardo Wurmus
2017-06-26 18:22 ` Francesco Potortì

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87k23znek5.fsf@users.sourceforge.net \
    --to=npostavs@users.sourceforge.net \
    --cc=27498@debbugs.gnu.org \
    --cc=rekado@elephly.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.