[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Debugging emacs memory management
From: |
Eli Zaretskii |
Subject: |
Re: Debugging emacs memory management |
Date: |
Mon, 21 Sep 2015 13:21:15 +0300 |
> Date: Mon, 21 Sep 2015 13:00:45 +0300
> From: Eli Zaretskii <address@hidden>
> Cc: address@hidden, address@hidden
>
> I will try to reproduce the problem on my machine; to help that,
> please tell me (a) what font/fontset-related customizations do you
> have, and (b) do you see the same problem when Emacs is started as
> "emacs -Q".
I tried to reproduce this on my machine, but couldn't. What I see is
that the chain of calls you reported happens only once, when the first
frame is created. When I later create a second frame, either with
"C-x 5 f" or by invoking emacsclient, x_new_font is indeed invoked
again, but it doesn't call Fset_char_table_range, and consequently no
additional sub-char-tables are allocated.
So I guess your customizations, in particular those related to fonts
and fontsets, are critical for debugging this problem.
Thanks.
- Re: Debugging emacs memory management, Dima Kogan, 2015/09/15
- Re: Debugging emacs memory management, Paul Eggert, 2015/09/16
- Re: Debugging emacs memory management, Dima Kogan, 2015/09/20
- Re: Debugging emacs memory management, Eli Zaretskii, 2015/09/21
- Re: Debugging emacs memory management, Dima Kogan, 2015/09/21
- Re: Debugging emacs memory management, Eli Zaretskii, 2015/09/21
- Re: Debugging emacs memory management,
Eli Zaretskii <=
- Re: Debugging emacs memory management, Dima Kogan, 2015/09/22
- Re: Debugging emacs memory management, Eli Zaretskii, 2015/09/23
- Re: Debugging emacs memory management, Dima Kogan, 2015/09/23
- Re: Debugging emacs memory management, Eli Zaretskii, 2015/09/23
Re: Debugging emacs memory management, Davis Herring, 2015/09/16
Re: Debugging emacs memory management, Markus Triska, 2015/09/16