From: Stefan Monnier <monnier@iro.umontreal.ca>
To: emacs-devel@gnu.org
Subject: Re: a few questions on current development master
Date: Sun, 10 Mar 2019 14:29:19 -0400 [thread overview]
Message-ID: <jwvk1h6oagk.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: 87wol64p18.fsf@ua2web.com
> 1) Memory issues. In almost no time it ate >6Gb of RSS and around 8GB or
> Virtual RAM. My OS: linux/arch, all default compilation options (no
> change to conigure flags).
Sounds like there's a bad leak.
> I will keep my eye on memory profiling, and will report more exact
> issues (profiler-start ram), any advice here?
We don't have a memory profiler: (profiler-start 'mem) simply uses
memory allocation as an approximation of time, but your problem is
likely not due to memory allocation but a lack of memory reclamation
(i.e. a leak).
> Also, quite strange that I've closed all buffers and still see that
> it consumes 6GB or RAM. Any documention how actually emacs returns
> RAM to host O/S ?
Returning memory to the OS can happen sometimes depending on lots of
different details, but it's basically irrelevant to your problem: If
there's a good reason why it got to 6GB, then returning to a smaller
size is good, but not indispensable. In your particular situation, IIUC
Emacs should simply not have gotten to 6GB in the first place.
> Should I just report all those as separte bugs via M-x report-emacs-bug?
Yes, please,
Stefan
next prev parent reply other threads:[~2019-03-10 18:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-10 17:28 a few questions on current development master Alex Koval
2019-03-10 17:51 ` Eli Zaretskii
2019-03-10 18:29 ` Stefan Monnier [this message]
2019-03-11 13:25 ` Daniel Pittman
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=jwvk1h6oagk.fsf-monnier+emacs@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=emacs-devel@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.