From: Markus Triska <markus.triska@gmx.at>
To: Chong Yidong <cyd@stupidchicken.com>
Cc: 1504@emacsbugs.donarmstrong.com
Subject: bug#1504: 23.0.60; emacs daemon leaks memory
Date: Sat, 06 Dec 2008 19:52:54 +0100 [thread overview]
Message-ID: <m1fxl1yw3d.fsf@gmx.at> (raw)
In-Reply-To: <87hc5hcg96.fsf@cyd.mit.edu> (Chong Yidong's message of "Sat, 06 Dec 2008 13:25:57 -0500")
Chong Yidong <cyd@stupidchicken.com> writes:
> Could you check whether this happens with the ordinary Emacs server as
When I do:
$ emacs -nw -Q --eval "(server-start)"
instead of "emacs -Q --daemon" above, it also uses more and more memory.
next prev parent reply other threads:[~2008-12-06 18:52 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-06 18:25 bug#1504: 23.0.60; emacs daemon leaks memory Chong Yidong
2008-12-06 18:52 ` Markus Triska [this message]
2008-12-07 1:15 ` Chong Yidong
2008-12-07 20:59 ` Markus Triska
-- strict thread matches above, loose matches on Subject: below --
2008-12-06 11:20 Markus Triska
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=m1fxl1yw3d.fsf@gmx.at \
--to=markus.triska@gmx.at \
--cc=1504@emacsbugs.donarmstrong.com \
--cc=cyd@stupidchicken.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.
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).