unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Daniel Clemente <dcl441-bugs@yahoo.com>
To: emacs-devel@gnu.org
Subject: Re: Memory leaks
Date: Mon, 10 Aug 2009 10:08:18 +0200	[thread overview]
Message-ID: <874osgozv1.fsf@CPU107.opentrends.net> (raw)
In-Reply-To: 87fxc2p1zv.fsf@cyd.mit.edu

El ds, ago 08 2009 a les 20:57, Chong Yidong va escriure:
>>   Hi, today my Emacs --daemon from CVS started eating memory and ended
>> …
>
> How quickly does this leak happen?  If you can make it leak quickly and
> reproducibly, the easiest approach is probably to bisect.

  This was caused by an Emacs which didn't do garbage collection and warned: „Building Emacs overflowed pure space“, due to a recent change already fixed. The full story is now explained at http://www.emacswiki.org/emacs/EmacsMemoryDebugging#toc9

  I also added your tip about bisecting.






  reply	other threads:[~2009-08-10  8:08 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-08-05 17:17 Memory leaks Daniel Clemente
2009-08-08 18:57 ` Chong Yidong
2009-08-10  8:08   ` Daniel Clemente [this message]
  -- strict thread matches above, loose matches on Subject: below --
2011-03-03 17:13 Uday S Reddy
2011-03-03 17:55 ` Andreas Schwab
2011-03-03 18:00   ` Uday S Reddy
2011-03-03 23:40     ` Andreas Schwab
2011-03-04 11:39       ` Uday S Reddy
2011-03-04 12:19         ` Eli Zaretskii
2011-03-04 12:59           ` Uday S Reddy
2011-03-07 19:19         ` Uday S Reddy
2011-03-07 20:33           ` Andreas Schwab
2011-03-07 22:27             ` David Kastrup
2011-03-07 22:49               ` David Kastrup
2011-03-09  0:39               ` Richard Stallman
2011-03-07 23:01             ` Uday S Reddy
2011-03-08  2:35               ` Stefan Monnier
2011-03-08  8:57                 ` Andreas Schwab
2011-03-09  0:40                   ` Richard Stallman
2011-03-09  6:07                     ` David Kastrup

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=874osgozv1.fsf@CPU107.opentrends.net \
    --to=dcl441-bugs@yahoo.com \
    --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).