unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: "Robert Thorpe" <rthorpe@realworldtech.com>
Subject: Re: emacs22 takes too much memory
Date: 18 Dec 2006 05:31:10 -0800	[thread overview]
Message-ID: <1166448670.075121.293410@t46g2000cwa.googlegroups.com> (raw)
In-Reply-To: <em3tns$eqk$1@news.yaako.com>

Ronald wrote:
> 130MB
>
> what's in use is:
> a. two tiny .c files
> b. cedet (semantic on)
> c. eshell
> d. other buffers opened automatically (scratch,Message,Completions)
>
> Why?

I can think of three possible reasons:-
* Top is reporting it wrong.  Top is notoriously inaccurate for
programs that use a lot of libraries.  In some circumstances it just
does program_space + library_space.  Check how much memory a simple
GTK+ app appears to be using, if it says ~100MB then that's the problem
* GTK+ another fairly notorious bit of software.  AFAIK It can consume
a lot of memory if used in ways the authors were not expecting.  Maybe
try the Xaw version?
* CEDET.  Maybe there is a strange interaction between new Emacs and
CEDET?  CEDET also uses a lot of memory, but it shouldn't use this much.

  parent reply	other threads:[~2006-12-18 13:31 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-12-17 17:11 emacs22 takes too much memory Ronald
2006-12-17 17:13 ` I installed it this way Ronald
2006-12-17 17:17 ` It's being opened nearlly half a day Ronald
2006-12-17 17:26 ` emacs22 takes too much memory Ralf Angeli
2006-12-17 17:46   ` Ronald
2006-12-17 18:00     ` Ralf Angeli
2006-12-17 18:34       ` Ronald
2006-12-17 18:49         ` Ralf Angeli
2006-12-17 19:17         ` Reiner Steib
2006-12-17 19:01 ` Peter Dyballa
2006-12-17 20:38   ` Eli Zaretskii
2006-12-17 21:11     ` Peter Dyballa
2006-12-18 13:31 ` Robert Thorpe [this message]
2006-12-19  2:13 ` Mark Hood

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=1166448670.075121.293410@t46g2000cwa.googlegroups.com \
    --to=rthorpe@realworldtech.com \
    /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.
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).