unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Peter Ludemann <peter.ludemann@gmail.com>
To: 38629@debbugs.gnu.org
Subject: bug#38629: Loading/killing the compilation output doesn't lose memory
Date: Sun, 15 Dec 2019 20:16:50 -0800	[thread overview]
Message-ID: <CAHjfyZ2_tEN=E1a1Fg9RyKxMphAmx4Tts=dLav=1dBzSihqueQ@mail.gmail.com> (raw)
In-Reply-To: <CAHjfyZ3Mfw+gqtyJie4Z2d=Je5bNYSouDPQ_t1wUsR4ZXVH2dw@mail.gmail.com>

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

If I save the *compilation* buffer and restart emacs, memory usage goes up
modestly when I load the file (52MB; it is automatically fontified by emacs
when I load it):

USER       PID %CPU %MEM    VSZ   RSS TTY      STAT START   TIME COMMAND
peter    19037  0.6  0.7 441776 115476 ?       Ssl  11:59   2:49 emacs
--daemon
peter    19037  0.6  1.0 495832 169776 ?       Ssl  11:59   2:50 emacs
--daemon

and memory usage returns to about the previous value when I kill the buffer
(I don't need to run 'garbage-collect).

So, the problems seems to be somewhere in the "compile" command:
(a) it uses a *lot* more memory than needed to display the result
(b) it doesn't free that memory when compilation ends or when the
compilation buffer is killed

My "compilation" is actually compile plus 8200 tests, speeding them up by
using GNU-parallel.

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

  reply	other threads:[~2019-12-16  4:16 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-12-15 19:58 bug#38629: 25.2; garbage-collect doesn't reclaim large *compilation* Peter Ludemann
2019-12-16  4:16 ` Peter Ludemann [this message]
2019-12-16 14:24 ` Noam Postavsky
2019-12-16 16:48   ` Peter Ludemann
2019-12-16 23:37   ` Peter Ludemann
2019-12-17  0:19     ` Peter Ludemann
2019-12-17 13:14       ` Noam Postavsky

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='CAHjfyZ2_tEN=E1a1Fg9RyKxMphAmx4Tts=dLav=1dBzSihqueQ@mail.gmail.com' \
    --to=peter.ludemann@gmail.com \
    --cc=38629@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 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).