From: Pip Cet <pipcet@gmail.com>
To: Will Bush <will.g.bush@gmail.com>
Cc: "Basil L. Contovounesios" <contovob@tcd.ie>,
40733@debbugs.gnu.org, James Cloos <cloos@jhcloos.com>,
Robert Pluim <rpluim@gmail.com>
Subject: bug#40733: 28.0.50; Emacs locks up on paste (yank) of unicode characters
Date: Mon, 1 Jun 2020 11:44:10 +0000 [thread overview]
Message-ID: <CAOqdjBfDRzbjdtEoJ7N126vSNtRbWp2uhbs7X+B5=eAvSjdQNQ@mail.gmail.com> (raw)
In-Reply-To: <CA+aYz4QssnSS3eMuYYkXOf8K-PZhKoVgo4bKLG-8hoJOVZBYBA@mail.gmail.com>
On Mon, Jun 1, 2020 at 11:20 AM Will Bush <will.g.bush@gmail.com> wrote:
> git clone https://github.com/adobe-fonts/adobe-blank.git
> cd adobe-blank
> sudo cp AdobeBlank.ttf /usr/share/fonts/
> fc-cache
> time emacs -Q --eval '(message "︵")' -kill
>
> And it took 4 minutes in the virtual machine!
> Please try it and see if you can repro!
It's taking a while here (pretty standard GNU/Linux x86_64 system),
but something on the order of 20 seconds, not 4 minutes.
in ftcrfont.c:
pat = ftfont_entity_pattern (entity, pixel_size);
FcConfigSubstitute (NULL, pat, FcMatchPattern);
FcDefaultSubstitute (pat);
match = FcFontMatch (NULL, pat, &result); <===========
ftfont_fix_match (pat, match);
This is where it spends so much time. "perf record emacs -Q" suggests
it's a function called FcCharSetSubtractCount. (You might try running
that on your setup, too).
next prev parent reply other threads:[~2020-06-01 11:44 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-20 11:05 bug#40733: 28.0.50; Emacs locks up on paste (yank) of unicode characters Will Bush
2020-04-20 15:52 ` Robert Pluim
2020-04-20 16:13 ` Eli Zaretskii
2020-04-20 21:27 ` Will Bush
2020-04-20 20:20 ` Alan Third
2020-04-20 22:48 ` Basil L. Contovounesios
2020-04-21 10:01 ` Robert Pluim
2020-04-21 12:19 ` Will Bush
2020-04-21 13:19 ` Robert Pluim
2020-04-21 19:35 ` James Cloos
2020-04-22 7:35 ` Robert Pluim
2020-04-25 10:34 ` Will Bush
[not found] ` <CA+aYz4RNB1-g5uUz-M-XuJEhZPGpA4X6n8NSiTCUdOMkpReFng@mail.gmail.com>
2020-04-25 13:34 ` bug#40733: Fwd: " Will Bush
2020-04-25 13:50 ` Eli Zaretskii
2020-04-29 11:59 ` Will Bush
2020-04-29 12:16 ` Eli Zaretskii
2020-04-29 12:42 ` Will Bush
2020-04-29 12:50 ` Robert Pluim
2020-04-29 14:30 ` Eli Zaretskii
2020-06-01 11:19 ` Will Bush
2020-06-01 11:44 ` Pip Cet [this message]
2020-06-01 15:15 ` Eli Zaretskii
2020-06-01 15:50 ` Pip Cet
2022-04-24 14:20 ` Lars Ingebrigtsen
2022-05-18 3:39 ` Will Bush
2022-05-18 11:18 ` Eli Zaretskii
2022-06-15 12:40 ` Lars Ingebrigtsen
2022-06-19 21:05 ` Will Bush
2022-06-19 22:25 ` Lars Ingebrigtsen
2020-04-21 14:29 ` 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='CAOqdjBfDRzbjdtEoJ7N126vSNtRbWp2uhbs7X+B5=eAvSjdQNQ@mail.gmail.com' \
--to=pipcet@gmail.com \
--cc=40733@debbugs.gnu.org \
--cc=cloos@jhcloos.com \
--cc=contovob@tcd.ie \
--cc=rpluim@gmail.com \
--cc=will.g.bush@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).