From: Dima Kogan <dima@secretsauce.net>
To: Eli Zaretskii <eliz@gnu.org>,Lars Ingebrigtsen <larsi@gnus.org>
Cc: dmantipov@yandex.ru, 21556@debbugs.gnu.org
Subject: bug#21556: 25.0.50; Memory leak in emacs -Q with lucid (font)
Date: Sun, 17 Nov 2019 13:27:35 -0800 [thread overview]
Message-ID: <D3FBAF8C-76B4-48DD-BBBF-4B829C7C126E@secretsauce.net> (raw)
In-Reply-To: <83v9ri5x8j.fsf@gnu.org>
Hi. I haven't gone memory-leak hunting in a while, but this patch did plug a sizeable hole with not clear ill effects. I think it's safe to close this bug.
next prev parent reply other threads:[~2019-11-17 21:27 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-25 0:05 bug#21556: 25.0.50; Memory leak in emacs -Q with lucid (font) Dima Kogan
2015-09-25 6:45 ` Eli Zaretskii
2015-09-25 6:57 ` Dima Kogan
2015-09-25 8:44 ` Eli Zaretskii
2015-09-25 8:13 ` Dima Kogan
2015-09-25 8:49 ` Eli Zaretskii
2015-09-25 9:10 ` Eli Zaretskii
2015-09-25 9:30 ` Dima Kogan
2015-09-25 9:45 ` Eli Zaretskii
2015-09-25 10:03 ` Eli Zaretskii
[not found] ` <83y4ftfbjw.fsf@gnu.org>
2015-09-27 7:56 ` K. Handa
2015-09-27 8:09 ` Eli Zaretskii
2015-09-28 9:22 ` Dima Kogan
2015-09-28 9:58 ` Eli Zaretskii
2015-09-29 9:28 ` Dima Kogan
2015-09-30 7:00 ` Eli Zaretskii
2015-09-30 10:16 ` Dmitry Antipov
2015-10-01 9:42 ` Dima Kogan
2015-10-01 13:27 ` Dmitry Antipov
2015-10-01 18:50 ` Dima Kogan
2015-10-02 5:04 ` Dmitry Antipov
2015-10-02 18:56 ` Dima Kogan
2015-10-29 22:51 ` Dima Kogan
2015-10-30 14:20 ` Eli Zaretskii
2015-10-30 19:17 ` Dima Kogan
2015-10-30 20:38 ` Eli Zaretskii
2015-10-30 20:50 ` Dima Kogan
2015-11-09 2:55 ` Dima Kogan
2015-11-09 16:38 ` Eli Zaretskii
2019-11-17 6:34 ` Lars Ingebrigtsen
2019-11-17 15:38 ` Eli Zaretskii
2019-11-17 21:27 ` Dima Kogan [this message]
2019-11-18 8:13 ` Lars Ingebrigtsen
2015-09-29 10:05 ` K. Handa
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=D3FBAF8C-76B4-48DD-BBBF-4B829C7C126E@secretsauce.net \
--to=dima@secretsauce.net \
--cc=21556@debbugs.gnu.org \
--cc=dmantipov@yandex.ru \
--cc=eliz@gnu.org \
--cc=larsi@gnus.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.