From: Madhu <enometh@meer.net>
To: help-gnu-emacs@gnu.org
Cc: 43395@debbugs.gnu.org
Subject: Re: memory leaks
Date: Tue, 10 Nov 2020 06:54:56 +0530 [thread overview]
Message-ID: <m3y2ja9f6f.fsf@leonis4.robolove.meer.net> (raw)
[Test case follows. Sorry Drew for trying to post to help-gnu and
debbugs simultaneously, but this is my third attempt at sending this
test case - I've tried sending it to debbugs.gnu.org and to
gmane.emacs.help newsgroup - and my messages have been dropped]
* Madhu <m35z8gise6.fsf@leonis4.robolove.meer.net> :
Wrote on Mon, 14 Sep 2020 15:36:57 +0530:
> The numbers I reported by garbage-collect do not account for the memory
> usage. FWIW I've posted that info again at
> https://debbugs.gnu.org/cgi/bugreport.cgi?bug=43395
I found test case for this bug and I sent mail to 43395@debbugs.gnu.org,
and qmail told me that the mail was accepted:
delivery 1: success:
209.51.188.43_accepted_message./Remote_host_said:_250_OK_id=1kc8Bf-00061T-3u/
But the bugreport didn't show up on gnu.emacs.bug.
Here is the test case:
#+BEGIN_SRC
$ cat > f.c
#include <stdio.h>
int
main()
{
char c = ' ';
while (c != 'q' && c != 'Q')
{
fprintf(stdout, "Press q then enter to quit: ");
c = fgetc(stdin);
}
return 0;
}
^D
$ gcc f.c
$ emacs -Q
#+END_SRC
M-x shell-command ./a.out
Then the process hangs. But Emacs' memory grows unbounded.
WARNING. Be careful to interrupt it with ^G before the OOM killer
kicks in. If you have swap you may lose control of your machine
indefinitely.
After you interrupt the sub process, Emacs is left with unreclaimed
gigabytes of RSS
Please let me know if you can reproduce this
next reply other threads:[~2020-11-10 1:24 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-10 1:24 Madhu [this message]
2020-11-10 15:16 ` memory leaks Eli Zaretskii
-- strict thread matches above, loose matches on Subject: below --
2019-09-20 7:23 Madhu
2019-09-20 8:00 ` Jean-Christophe Helary
2019-09-20 8:11 ` Eli Zaretskii
[not found] ` <mailman.572.1568967069.2190.help-gnu-emacs@gnu.org>
2019-09-20 8:31 ` Madhu
2019-09-20 9:21 ` Eli Zaretskii
[not found] ` <mailman.578.1568971399.2190.help-gnu-emacs@gnu.org>
2020-09-12 13:02 ` Madhu
2020-09-12 13:39 ` Eli Zaretskii
2020-09-12 13:55 ` Michael Heerdegen
2020-09-12 14:09 ` Eli Zaretskii
2020-09-12 19:14 ` Igor Sosa Mayor
2020-09-12 19:26 ` Eli Zaretskii
2020-09-12 19:28 ` Igor Sosa Mayor
2020-09-13 2:30 ` Eli Zaretskii
2020-09-13 3:17 ` Madhu
2020-09-13 14:14 ` Eli Zaretskii
2021-01-21 9:28 ` Madhu
2020-09-13 20:14 ` Stefan Monnier
2020-09-14 10:06 ` Madhu
2020-11-09 17:50 ` Madhu
2022-03-04 11:32 ` Eli Zaretskii
2022-03-06 10:59 ` Madhu
2022-03-06 11:15 ` Eli Zaretskii
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=m3y2ja9f6f.fsf@leonis4.robolove.meer.net \
--to=enometh@meer.net \
--cc=43395@debbugs.gnu.org \
--cc=help-gnu-emacs@gnu.org \
/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.
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).