From: David Hansen <david.hansen@gmx.net>
To: emacs-devel@gnu.org
Subject: Re: Memory leak
Date: Mon, 19 May 2008 15:34:20 +0200 [thread overview]
Message-ID: <87iqxa1kpv.fsf@localhorst.mine.nu> (raw)
In-Reply-To: E1Jy0NK-0000I6-BP@etlken.m17n.org
On Mon, 19 May 2008 17:05:42 +0900 Kenichi Handa wrote:
> I've just installed a fix in font-cache handling. Now, even
> when I create many new frames, the memory usage doesn't
> increase that much. Though it still increases several
> handreds K-bytes each time a new frame is created, and it is
> not reduced when I delete the frames. So, I think there
> still be a problem somewhere.
I used to have two frames open in my emacs session, never create or
destroy any other frames. Memory usage climbs to > 500M here after some
hours of usage. I doubt it has much to do with frame creation.
Will update right now and report back if your changes help.
David
next prev parent reply other threads:[~2008-05-19 13:34 UTC|newest]
Thread overview: 53+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-15 22:50 Memory leak Stefan Monnier
2008-05-15 23:06 ` David Kastrup
2008-05-16 0:25 ` Lennart Borgman (gmail)
2008-05-16 8:35 ` Eli Zaretskii
2008-05-16 9:03 ` Juanma Barranquero
2008-05-16 9:25 ` Eli Zaretskii
2008-05-16 9:29 ` Juanma Barranquero
2008-05-16 9:46 ` Eli Zaretskii
2008-05-16 9:49 ` Juanma Barranquero
2008-05-16 20:13 ` Stephen J. Turnbull
2008-05-16 21:15 ` [OT, silly] " Thomas Lord
2008-05-16 20:41 ` David Robinow
2008-05-16 21:36 ` Lennart Borgman (gmail)
2008-05-17 7:10 ` Eli Zaretskii
2008-05-16 9:43 ` Eli Zaretskii
2008-05-16 12:50 ` Jason Rumney
2008-05-19 8:05 ` Kenichi Handa
2008-05-19 8:45 ` YAMAMOTO Mitsuharu
2008-05-19 11:13 ` Kenichi Handa
2008-05-19 11:59 ` YAMAMOTO Mitsuharu
2008-05-23 2:24 ` Kenichi Handa
2008-05-19 13:34 ` David Hansen [this message]
2008-05-19 19:42 ` David Hansen
2008-05-24 2:30 ` calculation of text extents [Re: Memory leak] Kenichi Handa
2008-05-16 2:19 ` Memory leak Stefan Monnier
2008-05-16 0:38 ` YAMAMOTO Mitsuharu
2008-05-17 15:16 ` Evil Boris
2008-05-17 19:11 ` Stephen J. Turnbull
2008-05-17 19:17 ` Eric Hanchrow
2008-05-18 11:26 ` Jan Djärv
2008-05-18 11:29 ` David Kastrup
2008-05-20 6:46 ` Jan Djärv
2008-05-18 13:34 ` Werner LEMBERG
2008-05-20 6:48 ` Jan Djärv
2008-05-19 2:44 ` Stephen J. Turnbull
2008-05-20 6:50 ` Jan Djärv
2008-05-21 6:10 ` Stephen J. Turnbull
2008-05-21 17:32 ` Stefan Monnier
2008-05-23 13:54 ` Evil Boris
-- strict thread matches above, loose matches on Subject: below --
2008-05-30 22:39 memory leak Drew Adams
2008-05-31 7:57 ` David Kastrup
2008-05-24 23:02 Memory leak Nick Roberts
2006-04-28 17:51 memory leak Robert J. Chassell
2006-04-28 18:10 ` Andreas Schwab
2006-04-28 20:25 ` Robert J. Chassell
2006-04-29 1:56 ` Luc Teirlinck
2006-04-29 11:16 ` Robert J. Chassell
2006-04-29 14:06 ` Luc Teirlinck
2006-04-29 16:41 ` Robert J. Chassell
2006-04-29 17:07 ` Luc Teirlinck
2006-04-29 19:32 ` Robert J. Chassell
2006-04-30 3:03 ` Richard Stallman
2006-04-30 4:15 ` Luc Teirlinck
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=87iqxa1kpv.fsf@localhorst.mine.nu \
--to=david.hansen@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 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).