From: "René Kuligowski" <renekuligowski@o2mail.de>
To: 34320@debbugs.gnu.org
Subject: bug#34320: Fwd: Re: bug#34320: Emacs 26.1: RAM does not get released after quitting Emacs
Date: Tue, 05 Feb 2019 11:45:29 -0100 [thread overview]
Message-ID: <5C598569.30304@o2mail.de> (raw)
In-Reply-To: <5C58AF7C.3000005@o2mail.de>
For completeness ;-)
I also checked thoroughly in the VFSes (/sys, /proc etc.) and ran a
mem tracer. The memory blocks are not freed, but stay allocated, like
from a forgotten free() call or a severely buggy malloc() call (like the
common issues with gcc 3.3 and 4.5).
Since I use gcc 4.4 (quite reliable in my experience), my question
is: is Emacs 26 using mem alloc calls which are revised/defined in
C-2011 or C-2015 standards, and not likely to be properly available in
older compilers? That might be an explanation, though not exactly the
„cure“ for the problem.
Regards,
R.Kuligowski
-------- Original Message --------
Subject: Re: bug#34320: Emacs 26.1: RAM does not get released after
quitting Emacs
Date: Tue, 05 Feb 2019 07:34:10 -0100
From: René Kuligowski <renekuligowski@o2mail.de>
To: Glenn Morris <rgm@gnu.org>
Sorry, the last answer was a bit short.
Reasons why neither is the case:
doing 'ps axf | grep emacs' shows only the grep call itself. Without
grepping, there is no hint of either emacs or a died/zombie process
eating up memory.
the '+/- cache' line of free shows the amounts I stated, the first one
is always about 1GB larger due to cache buffers.
On 04.02.2019 22:48, Glenn Morris wrote:
> Either the process hasn't actually exited, or you are confused by memory
> used for file cache. Ref eg https://www.linuxatemyram.com/
>
>
>
next prev parent reply other threads:[~2019-02-05 12:45 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-04 21:32 bug#34320: Emacs 26.1: RAM does not get released after quitting Emacs René Kuligowski
2019-02-04 23:48 ` Glenn Morris
2019-02-05 12:45 ` René Kuligowski [this message]
2019-02-05 17:20 ` bug#34320: Fwd: " Eli Zaretskii
2019-02-06 21:46 ` René Kuligowski
2019-02-06 22:22 ` René Kuligowski
2019-02-20 21:19 ` René Kuligowski
2019-02-20 19:30 ` 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5C598569.30304@o2mail.de \
--to=renekuligowski@o2mail.de \
--cc=34320@debbugs.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.
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.