all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Stephen Berman <Stephen.Berman@gmx.net>
To: emacs-devel@gnu.org
Subject: Re: memory usage
Date: Mon, 09 Jul 2007 15:01:40 +0200	[thread overview]
Message-ID: <87ir8tn32j.fsf@escher.local.home> (raw)
In-Reply-To: 87y7ik6hx1.fsf@escher.local.home

I accidentally posted the below in the wrong thread; this is the right
one.

On Mon, 09 Jul 2007 11:06:24 +0200 Stephen Berman <Stephen.Berman@gmx.net> wrote:

> Update: After my last post in this thread on 15 Jun 2007 I continued
> alternating between using the released Emacs 22.1 and the CVS trunk
> builds from 4/30 and 6/3.  The latter continued to show increased
> memory usage, the first two did not show this.  On 19 Jun 2007 Jason
> Rumney <jasonr@gnu.org> wrote in other thread (see
> http://permalink.gmane.org/gmane.emacs.devel/73303):
>
>> There was a brief period where changes in image.c caused a memory leak,
>> and on Windows a GDI resource leak (which caused crashes when the
>> resources allocated reached 9999, after 5-10 minutes of typical use for
>> me). But that was fixed more than a week ago, and was more of a problem
>> on other branches where the fix wasn't merged for until this weekend
>> just gone.
>
> On 6/30 I updated from CVS trunk to my current build, which I've used
> daily since and have not experienced increased memory usage with it.
> So I assume my build from 6/3 had the memory leak, which has since
> been fixed.
>
> Steve Berman

      reply	other threads:[~2007-07-09 13:01 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-06-11 20:36 memory usage Stephen Berman
2007-06-11 21:28 ` Stefan Monnier
2007-06-13 16:21 ` Richard Stallman
2007-06-13 17:59   ` Stephen Berman
2007-06-14 16:19     ` Richard Stallman
2007-06-14 19:09       ` Stephen Berman
2007-06-15 19:21         ` Richard Stallman
2007-06-15 21:12           ` Stephen Berman
2007-07-09 13:01             ` Stephen Berman [this message]

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=87ir8tn32j.fsf@escher.local.home \
    --to=stephen.berman@gmx.net \
    --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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.