From: Eli Zaretskii <eliz@gnu.org>
To: Ken Raeburn <raeburn@permabit.com>
Cc: monnier@iro.umontreal.ca, 11822@debbugs.gnu.org
Subject: bug#11822: 24.1; emacsclient terminal mode captures escape characters as text
Date: Fri, 25 Sep 2015 09:49:04 +0300 [thread overview]
Message-ID: <83io6zhu3j.fsf@gnu.org> (raw)
In-Reply-To: <CAJJWxE9bE-DvRjNqcHwOP3wSHjubw1aZ=SMaMbygSgOxV-o1fA@mail.gmail.com>
> Date: Thu, 24 Sep 2015 16:08:04 -0400
> From: Ken Raeburn <raeburn@permabit.com>
> Cc: Stefan Monnier <monnier@iro.umontreal.ca>, 11822@debbugs.gnu.org
>
> > In this run, I recorded over 601000 bytes being allocated; about 60% of
> that (~364000) was done from things called by parse_single_submenu; about
> half of that (~185000), in turn, was via larger_vector called from
> ensure_menu_items. The largest of those was a single allocation of 62000
> bytes. There were several more of these calls, with smaller sizes, and
> varying in the nesting depth of single_menu_item and friends.
>
> Can you show the backtrace from the 62000-byte allocation?
>
>
> Hardware watchpoint 3: consing_since_gc
>
> Old value = 236408
> New value = 298408
> allocate_vectorlike (len=7749) at ../../src/alloc.c:3129
> 3129 vector_cells_consed += len;
> #0 allocate_vectorlike (len=7749) at ../../src/alloc.c:3129
> #1 0x000000000053c358 in XUNTAG (type=<optimized out>, a=<optimized out>) at .
> ./../src/lisp.h:839
> #2 XVECTOR (a=<optimized out>) at ../../src/lisp.h:969
> #3 allocate_vectorlike (len=7749) at ../../src/alloc.c:3097
> #4 allocate_vector (len=7749) at ../../src/alloc.c:3148
> #5 0x000000000055febd in larger_vector (vec=20730845, incr_min=<optimized out>,
> nitems_max=<optimized out>) at ../../src/fns.c:3619
> #6 0x0000000000463c18 in ensure_menu_items (items=<optimized out>) at .
> ./../src/menu.c:172
> #7 0x0000000000463dbe in push_menu_item (name=8891140, enable=44016,
> key=7152208, def=4131552, equiv=0, type=0, selected=0, help=0) at .
> ./../src/menu.c:242
> #8 0x00000000004640ae in single_menu_item (skp_v=0x7fffffffcbf0, key=7152208,
> item=<optimized out>, dummy=<optimized out>) at ../../src/menu.c:424
> #9 single_menu_item (key=7152208, item=<optimized out>, dummy=<optimized out>,
> skp_v=0x7fffffffcbf0) at ../../src/menu.c:322
> #10 0x00000000004f468a in map_keymap_item (data=0x7fffffffcbf0, val=<optimized
> out>, key=<optimized out>, args=0, fun=0x463ea0 <single_menu_item>) at .
> ./../src/keymap.c:547
> #11 map_keymap_internal (map=19459395, fun=0x463ea0 <single_menu_item>, args=0,
> data=0x7fffffffcbf0) at ../../src/keymap.c:584
> #12 0x0000000000463d18 in single_keymap_panes (keymap=16111731,
> pane_name=<optimized out>, prefix=<optimized out>, maxdepth=8) at .
> ./../src/menu.c:298
> #13 0x0000000000464124 in single_menu_item (skp_v=0x7fffffffcd50, key=5159696,
> item=<optimized out>, dummy=<optimized out>) at ../../src/menu.c:437
> #14 single_menu_item (key=5159696, item=<optimized out>, dummy=<optimized out>,
> skp_v=0x7fffffffcd50) at ../../src/menu.c:322
> #15 0x00000000004f468a in map_keymap_item (data=0x7fffffffcd50, val=<optimized
> out>, key=<optimized out>, args=0, fun=0x463ea0 <single_menu_item>) at .
> ./../src/keymap.c:547
> #16 map_keymap_internal (map=19467347, fun=0x463ea0 <single_menu_item>, args=0,
> data=0x7fffffffcd50) at ../../src/keymap.c:584
> #17 0x0000000000463d18 in single_keymap_panes (keymap=19716755,
> pane_name=<optimized out>, prefix=<optimized out>, maxdepth=9) at .
> ./../src/menu.c:298
> #18 0x0000000000464124 in single_menu_item (skp_v=0x7fffffffceb0, key=8138816,
> item=<optimized out>, dummy=<optimized out>) at ../../src/menu.c:437
> #19 single_menu_item (key=8138816, item=<optimized out>, dummy=<optimized out>,
> skp_v=0x7fffffffceb0) at ../../src/menu.c:322
> #20 0x00000000004f468a in map_keymap_item (data=0x7fffffffceb0, val=<optimized
> out>, key=<optimized out>, args=0, fun=0x463ea0 <single_menu_item>) at .
> ./../src/keymap.c:547
> #21 map_keymap_internal (map=19488483, fun=0x463ea0 <single_menu_item>, args=0,
> data=0x7fffffffceb0) at ../../src/keymap.c:584
> #22 0x0000000000463d18 in single_keymap_panes (keymap=19750115,
> pane_name=<optimized out>, prefix=<optimized out>, maxdepth=10) at .
> ./../src/menu.c:298
> #23 0x00000000004652c8 in parse_single_submenu (item_key=8191056,
> item_name=9330724, maps=<optimized out>) at ../../src/menu.c:566
> #24 0x0000000000466a9f in set_frame_menubar (f=0x122a940, first_time=<optimized
> out>, deep_p=<optimized out>) at ../../src/xmenu.c:797
> #25 0x00000000004d0038 in Fx_create_frame (parms=13618675) at .
> ./../src/xfns.c:3307
Looks like some deeply recursive keymap? Can you show the values of
relevant variables, so that we could have an idea which keymap is that?
> I'm still seeing no display problems with the test branch; I'm fine with
> closing out this ticket now.
Great, I will merge the branch soon.
Thanks.
next prev parent reply other threads:[~2015-09-25 6:49 UTC|newest]
Thread overview: 64+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-30 0:08 bug#11822: 24.1; emacsclient terminal mode captures escape characters as text Ken Raeburn
2012-06-30 5:55 ` Eli Zaretskii
2012-07-31 21:06 ` Ken Raeburn
2012-08-08 3:13 ` Ken Raeburn
2012-08-08 4:52 ` Dan Nicolaescu
2012-08-08 9:26 ` Ken Raeburn
2012-08-09 21:12 ` Ken Raeburn
2012-08-10 6:16 ` Eli Zaretskii
2012-08-10 7:27 ` Ken Raeburn
2012-08-10 7:46 ` Eli Zaretskii
2012-08-10 8:08 ` Eli Zaretskii
2015-09-07 21:09 ` Ken Raeburn
2015-09-08 1:29 ` Stefan Monnier
2015-09-08 4:29 ` Eli Zaretskii
2015-09-08 6:53 ` Ken Raeburn
2015-09-08 13:03 ` Stefan Monnier
2015-09-08 13:11 ` Stefan Monnier
2015-09-08 17:21 ` Eli Zaretskii
2015-09-08 4:48 ` Eli Zaretskii
2015-09-08 10:15 ` Ken Raeburn
2015-09-08 13:35 ` Stefan Monnier
2015-09-08 17:33 ` Eli Zaretskii
2015-09-08 19:54 ` Ken Raeburn
2015-09-09 14:16 ` Eli Zaretskii
2015-09-10 6:59 ` Ken Raeburn
2015-09-10 15:36 ` Eli Zaretskii
2015-09-10 17:56 ` Stefan Monnier
2015-09-10 18:06 ` Eli Zaretskii
2015-09-11 12:56 ` Stefan Monnier
2015-09-11 13:53 ` Eli Zaretskii
2015-09-11 16:53 ` Stefan Monnier
2015-09-11 6:54 ` Ken Raeburn
2015-09-11 7:22 ` Eli Zaretskii
2015-09-11 23:11 ` Ken Raeburn
2015-09-12 0:51 ` Stefan Monnier
2015-09-12 1:34 ` Ken Raeburn
2015-09-15 14:29 ` Eli Zaretskii
2015-09-15 16:14 ` Stefan Monnier
2015-09-18 14:19 ` Eli Zaretskii
2015-09-21 9:23 ` Ken Raeburn
2015-09-21 9:44 ` Eli Zaretskii
2015-09-23 17:27 ` Ken Raeburn
2015-09-23 18:04 ` martin rudalics
2015-09-23 20:59 ` Ken Raeburn
2015-09-23 19:17 ` Eli Zaretskii
2015-09-24 8:52 ` Ken Raeburn
2015-09-24 18:46 ` Eli Zaretskii
2015-09-24 20:08 ` Ken Raeburn
2015-09-25 6:49 ` Eli Zaretskii [this message]
2015-09-25 12:07 ` Stefan Monnier
2015-09-26 7:01 ` Eli Zaretskii
2015-09-25 6:50 ` Eli Zaretskii
2015-09-25 12:09 ` Stefan Monnier
2015-09-25 13:29 ` Eli Zaretskii
2015-09-25 15:18 ` Stefan Monnier
2015-09-12 7:30 ` Eli Zaretskii
2015-09-11 13:39 ` Stefan Monnier
2015-09-11 14:01 ` Eli Zaretskii
2015-09-08 13:22 ` Stefan Monnier
2015-09-08 17:25 ` Eli Zaretskii
2015-09-08 18:52 ` Stefan Monnier
2015-09-08 19:08 ` Eli Zaretskii
2015-09-08 20:37 ` Stefan Monnier
2015-09-08 17:36 ` 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=83io6zhu3j.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=11822@debbugs.gnu.org \
--cc=monnier@iro.umontreal.ca \
--cc=raeburn@permabit.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).