unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Dima Kogan <dima@secretsauce.net>
To: martin rudalics <rudalics@gmx.at>
Cc: 21509@debbugs.gnu.org
Subject: bug#21509: 25.0.50; X11 error: BadPixmap when creating first emacsclient frame; and memory leak
Date: Mon, 16 Oct 2017 09:33:01 -0700	[thread overview]
Message-ID: <878tgbvyrm.fsf@shorty> (raw)
In-Reply-To: <59E462D1.5060300@gmx.at>

martin rudalics <rudalics@gmx.at> writes:

> What surprises me is that both 800K cons-threshold runs apparently start
> with a considerable lower memory consumption (around 20000 kB) than the
> 80k and 8000k runs.

Ah, that I CAN explain: it's an artifact of the way I ran the trials.

For the 800k cases I'd start the emacs daemon from the commandline, and
then start gathering the data and cycling the frames.

For the 80k and 8000k cases I'd start the daemon, and then take an
extra step:

  Open a single client frame to (setq gc-cons-threshold whatever)

I should have started gathering the usage data before I opened this
first frame, but I guess I didn't. So the memory usage plots the 800k
start when no frames have ever been created, but the 80k and 8000k start
after 1 frame was created.

So this difference isn't indicative of anything interesting.





  reply	other threads:[~2017-10-16 16:33 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-18  4:41 bug#21509: 25.0.50; X11 error: BadPixmap when creating first emacsclient frame; and memory leak Dima Kogan
     [not found] ` <handler.21509.B.14425512741008.ack@debbugs.gnu.org>
2015-10-02  7:32   ` bug#21509: update Dima Kogan
2017-09-03 10:15 ` bug#21509: 25.0.50; X11 error: BadPixmap when creating first emacsclient frame; and memory leak martin rudalics
2017-09-05  6:21   ` Dima Kogan
2017-09-05  8:18     ` martin rudalics
2017-09-09  1:49       ` Dima Kogan
2017-09-09  7:59         ` martin rudalics
2017-10-15  3:48           ` Dima Kogan
2017-10-15  9:40             ` martin rudalics
2017-10-15 18:24               ` Dima Kogan
2017-10-16  7:42                 ` martin rudalics
2017-10-16 16:33                   ` Dima Kogan [this message]
2017-10-17  8:58                     ` martin rudalics

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=878tgbvyrm.fsf@shorty \
    --to=dima@secretsauce.net \
    --cc=21509@debbugs.gnu.org \
    --cc=rudalics@gmx.at \
    /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).