Gnus development mailing list
 help / color / mirror / Atom feed
From: kai.grossjohann@gmx.net (Kai Großjohann)
Subject: Re: Lisp pointer size warning?
Date: Mon, 09 Jun 2003 11:18:03 +0200	[thread overview]
Message-ID: <84vfvfk3sk.fsf@lucy.is.informatik.uni-duisburg.de> (raw)
In-Reply-To: <uisrgvugk.fsf@adobe.com>

Danny Siu <dsiu@adobe.com> writes:

> I have been observing the similar memory warnings after I added: (add-hook
> 'gnus-select-article-hook 'gnus-agent-fetch-selected-article)

I have this, too.

> With the above removed, I don't see the warning as often.  It only after I
> do many (20+) 'J s' does the warning appear.  I see the Emacs memory usage
> (with task manager on WinXP) increases 100-500K whenever I do 'J s'.

I wonder where is that memory going?
-- 
This line is not blank.



  reply	other threads:[~2003-06-09  9:18 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-06-05 16:19 Mattias Ahnberg
2003-06-05 20:51 ` Kai Großjohann
2003-06-09  2:46   ` Danny Siu
2003-06-09  9:18     ` Kai Großjohann [this message]
2003-06-09  9:24       ` Danny Siu
2003-06-12 22:28         ` Dave Love
2003-06-09 10:42     ` Mattias Ahnberg

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=84vfvfk3sk.fsf@lucy.is.informatik.uni-duisburg.de \
    --to=kai.grossjohann@gmx.net \
    /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 NNTP newsgroup(s).