From: Eli Zaretskii <eliz@gnu.org>
To: Nick OBrien <nick4f42@proton.me>
Cc: 69246@debbugs.gnu.org
Subject: bug#69246: 30.0.50; persistent key input delay after using vc commands in pgtk
Date: Mon, 19 Feb 2024 05:28:31 +0200 [thread overview]
Message-ID: <86a5nxqgio.fsf@gnu.org> (raw)
In-Reply-To: <niFhknZWw2Lrd6KNxQ6dwUSuYTJ7OmF2qZjUmsU8ZBTGjloS-J-gRDFXaCRCv7k8lVUFheweosfgDPeJmwzHN77oCR4UYGmjG1rHd9A_UHc=@proton.me> (message from Nick OBrien on Sun, 18 Feb 2024 20:36:46 +0000)
> Date: Sun, 18 Feb 2024 20:36:46 +0000
> From: Nick OBrien <nick4f42@proton.me>
> Cc: 69246@debbugs.gnu.org
>
> I ran the profiler twice: once before the input lag started, and once after.
> Each time, I ran M-x profiler-start RET RET, repeated C-f C-b for roughly 20
> seconds, then ran M-x profiler-stop and M-x profiler-report.
>
> In the foo buffer before running vc-annotate (no noticeable input delay):
>
> 44 63% - command-execute
> 44 63% - byte-code
> 44 63% - read-extended-command
> 44 63% - read-extended-command-1
> 44 63% - completing-read-default
> 13 18% redisplay_internal (C function)
> 24 34% redisplay_internal (C function)
> 1 1% - undo-auto--add-boundary
> 1 1% undo-auto--boundaries
> 0 0% ...
>
> In the foo buffer after running vc-annotate, pressing p p n n, and killing the
> vc-annotate buffer (noticeable input delay):
>
> 43 72% - command-execute
> 42 71% - byte-code
> 42 71% - read-extended-command
> 42 71% - read-extended-command-1
> 42 71% - completing-read-default
> 4 6% redisplay_internal (C function)
> 2 3% - command-execute
> 2 3% interactive-form
> 1 1% - funcall-interactively
> 1 1% execute-extended-command
> 13 22% redisplay_internal (C function)
> 3 5% - timer-event-handler
> 3 5% - apply
> 2 3% - show-paren-function
> 1 1% show-paren--default
> 1 1% - #<subr F616e6f6e796d6f75732d6c616d626461_anonymous_lambda_9>
> 1 1% jit-lock-context-fontify
> 0 0% ...
Thanks, but I don't see anything here which gives a hint why you see
the lags, nor even evidence that there was a lag. Maybe try leaning
on a key for 20 seconds, so that the keyboard auto-repeat produces
keypresses at high frequency -- maybe then the profile will tell
something.
next prev parent reply other threads:[~2024-02-19 3:28 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-17 20:38 bug#69246: 30.0.50; persistent key input delay after using vc commands in pgtk Nick OBrien via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-02-18 19:04 ` Eli Zaretskii
2024-02-18 19:21 ` Nick OBrien via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-02-18 19:31 ` Eli Zaretskii
2024-02-18 20:36 ` Nick OBrien via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-02-19 3:28 ` Eli Zaretskii [this message]
2024-02-21 2:19 ` Nick OBrien via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-02-21 12:41 ` Eli Zaretskii
2024-02-21 12:49 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-02-21 16:09 ` Nick OBrien via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-02-22 1:20 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-02-22 6:45 ` Eli Zaretskii
2024-02-22 8:02 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-02-22 8:23 ` Eli Zaretskii
2024-02-22 8:51 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-02-24 22:24 ` Nick OBrien via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-02-25 5:55 ` 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=86a5nxqgio.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=69246@debbugs.gnu.org \
--cc=nick4f42@proton.me \
/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).