From: Eli Zaretskii <eliz@gnu.org>
To: Nikolay Kudryavtsev <nikolay.kudryavtsev@gmail.com>
Cc: 24565@debbugs.gnu.org
Subject: bug#24565: 25.1: info freezes on some elements
Date: Sat, 01 Oct 2016 12:17:46 +0300 [thread overview]
Message-ID: <83twcwl96t.fsf@gnu.org> (raw)
In-Reply-To: <d82aba78-309e-df77-2052-80eb7b9ed49f@gmail.com> (message from Nikolay Kudryavtsev on Sat, 1 Oct 2016 11:55:44 +0300)
> From: Nikolay Kudryavtsev <nikolay.kudryavtsev@gmail.com>
> Cc: 24565@debbugs.gnu.org
> Date: Sat, 1 Oct 2016 11:55:44 +0300
>
> That commit removed defines that effectively commented out
> compact_font_cache_entry on Windows
Indeed, and on purpose. That code was ifdef'ed away because it caused
serious problems on Windows that couldn't be resolved for the next
release. Now they are mostly resolved, so having some code run on
most platforms, but not on Windows, is bad for maintainability.
In particular, not compacting the font cache can potentially bloat the
Emacs memory footprint to humongous proportions, although this only
happens in some rare scenarios.
> comment there links to #15876, which seems to be the original report
> for this bug.
AFAIR, we never got to the bottom of that bug, but perhaps it indeed
has the same reason.
I'm sorry, but none of the active developers here know enough about
font handling in Emacs to fix these issues in a more thorough way. So
for the time being, if some specific rarely-used font causes
performance degradation, and no simple and safe fix could be found,
the only remedy is to refrain from using that particular font.
next prev parent reply other threads:[~2016-10-01 9:17 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-29 7:30 bug#24565: 25.1: info freezes on some elements Nikolay Kudryavtsev
2016-09-29 15:13 ` Eli Zaretskii
2016-09-30 10:50 ` Nikolay Kudryavtsev
2016-09-30 12:22 ` Eli Zaretskii
2016-09-30 15:03 ` Nikolay Kudryavtsev
2016-09-30 16:14 ` Eli Zaretskii
2016-10-01 8:14 ` Nikolay Kudryavtsev
2016-10-01 8:45 ` Eli Zaretskii
2016-10-01 8:55 ` Nikolay Kudryavtsev
2016-10-01 9:17 ` Eli Zaretskii [this message]
2016-10-01 9:32 ` Nikolay Kudryavtsev
2016-10-01 9:48 ` Eli Zaretskii
2016-10-08 19:37 ` Eli Zaretskii
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=83twcwl96t.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=24565@debbugs.gnu.org \
--cc=nikolay.kudryavtsev@gmail.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).