unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Alex Koval <alex@koval.kharkov.ua>
Cc: emacs-devel@gnu.org
Subject: Re: a few questions on current development master
Date: Sun, 10 Mar 2019 19:51:19 +0200	[thread overview]
Message-ID: <83pnqy62js.fsf@gnu.org> (raw)
In-Reply-To: <87wol64p18.fsf@ua2web.com> (message from Alex Koval on Sun, 10 Mar 2019 19:28:35 +0200)

> From: Alex Koval <alex@koval.kharkov.ua>
> Date: Sun, 10 Mar 2019 19:28:35 +0200
> 
> 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.
> 
>    I will keep my eye on memory profiling, and will report more exact
>    issues (profiler-start ram), any advice here?

My advice is not to use the memory profiling as a means to dig into
this problem.  Unlike its name, memory profiling has nothing to do
with profiling memory usage.

> Should I just report all those as separte bugs via M-x report-emacs-bug?

Yes, please.  With all the details you can provide, and preferably
starting from "emacs -Q".

Thanks.



  reply	other threads:[~2019-03-10 17:51 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 [this message]
2019-03-10 18:29 ` Stefan Monnier
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

  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=83pnqy62js.fsf@gnu.org \
    --to=eliz@gnu.org \
    --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).