From: Paul Eggert <eggert@cs.ucla.edu>
To: 19147@debbugs.gnu.org
Subject: bug#19147: 25.0.50; Emacs daemon: leaking memory in a tight loop after losing X frame.
Date: Tue, 25 Nov 2014 22:12:31 -0800 [thread overview]
Message-ID: <54756F4F.4010701@cs.ucla.edu> (raw)
In-Reply-To: <ks7fyoxglt.fsf@netfonds.no>
Is this the well-known Gtk bug? See:
http://bugs.gnu.org/3360
http://bugs.gnu.org/5386
http://bugs.gnu.org/5535
etc.
next prev parent reply other threads:[~2014-11-26 6:12 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-21 23:45 bug#19147: 25.0.50; Emacs daemon: leaking memory in a tight loop after losing X frame Peder O. Klingenberg
2014-11-26 6:12 ` Paul Eggert [this message]
2014-11-26 16:27 ` Dmitry Antipov
2014-12-11 10:47 ` Dmitry Antipov
2014-12-11 12:27 ` Peder O. Klingenberg
2014-12-15 15:54 ` Óscar Fuentes
2014-12-15 16:04 ` Dmitry Antipov
2014-12-15 16:14 ` Óscar Fuentes
2014-12-15 19:57 ` Stefan Monnier
2014-12-16 13:19 ` Dmitry Antipov
2014-12-16 14:13 ` Stefan Monnier
2015-05-14 15:40 ` Jan Djärv
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=54756F4F.4010701@cs.ucla.edu \
--to=eggert@cs.ucla.edu \
--cc=19147@debbugs.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).