unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Daniel Pittman <slippycheeze@google.com>
To: Alex Koval <alex@koval.kharkov.ua>
Cc: emacs-devel <emacs-devel@gnu.org>
Subject: Re: a few questions on current development master
Date: Mon, 11 Mar 2019 09:25:19 -0400	[thread overview]
Message-ID: <CAC45yQsMd+2CB1bLBvVy2P61cBxQ7uRNmM02pwjAO7Om+i6tKw@mail.gmail.com> (raw)
In-Reply-To: <87wol64p18.fsf@ua2web.com>

[-- Attachment #1: Type: text/plain, Size: 1255 bytes --]

On Sun, Mar 10, 2019 at 1:29 PM Alex Koval <alex@koval.kharkov.ua> wrote:

> I've been using emacs-27.0.50 built from git for quite a some time, no
> issues were found until recently.
>
> Yesterday I've installed the latest version from source and got a few
> issues with it.
>
> 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).
>
>    Just to compare it, I've worked with same code in same project but with
>    emacs-26.1.92 for another 6 hours and it only consumed 1.2Gb so far.
>

FWIW, I checked my Emacs instance – uptime 3 days, 21 hours – and I have
112.8MB private memory, 196.6 total (including OS toolkit memory returnable
to the OS) on macOS.  So, while I'm uncertain what our comparative load is,
I'm definitely not seeing similar numbers on a build from last Thursday.
This is on macOS, but past experience says that platform is more likely,
not less, to show excessive memory use.

I'm assuming that this is almost all private memory (that is, a leak, as
Eli says) but
https://raw.githubusercontent.com/pixelb/ps_mem/master/ps_mem.py will print
a useful summary and confirm that.

[-- Attachment #2: Type: text/html, Size: 1714 bytes --]

      parent reply	other threads:[~2019-03-11 13:25 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
2019-03-11 13:25 ` Daniel Pittman [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=CAC45yQsMd+2CB1bLBvVy2P61cBxQ7uRNmM02pwjAO7Om+i6tKw@mail.gmail.com \
    --to=slippycheeze@google.com \
    --cc=alex@koval.kharkov.ua \
    --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 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).