From: "Francesco Potortì" <Potorti@isti.cnr.it>
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 20:22:39 +0200 [thread overview]
Message-ID: <E1dPYel-0008A9-M8@tucano.isti.cnr.it> (raw)
In-Reply-To: <87lgofko1i.fsf@elephly.net>
>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 may be a duplicate of #26952
prev parent reply other threads:[~2017-06-26 18:22 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
2017-06-26 13:14 ` Ricardo Wurmus
2017-06-27 5:17 ` Ricardo Wurmus
2017-06-26 18:22 ` Francesco Potortì [this message]
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=E1dPYel-0008A9-M8@tucano.isti.cnr.it \
--to=potorti@isti.cnr.it \
--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 public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).