unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Andrey Orst <andreyorst@gmail.com>
Cc: 46350@debbugs.gnu.org
Subject: bug#46350: 28.0.50; touchpad-scrolling-eats-lots-of-cpu-samples
Date: Sat, 06 Feb 2021 19:59:23 +0200	[thread overview]
Message-ID: <83a6shnklg.fsf@gnu.org> (raw)
In-Reply-To: <CAAKhXobpGN2iUxHYkYRx8Ma7Gh=cSOGU=m3z2FYF_fJ2nU7bLg@mail.gmail.com> (message from Andrey Orst on Sat, 6 Feb 2021 20:33:56 +0300)

> From: Andrey Orst <andreyorst@gmail.com>
> Date: Sat, 6 Feb 2021 20:33:56 +0300
> 
> 1. Run emacs -q
> 2. Open some big file, in my case I've opened lisp-mode.el
> 3. Turn on fundamental-mode (optional)
> 4. Go to the end of the buffer.
> 5. Rapidly produce scroll up events from touchpad or mouse wheel
>    (although it is much harder to achieve with mouse) with significant
>    scroll amount.  By significant scroll amount I mean continuous
>    scrolling event from touchpad, which can be achieved by swiping over
>    whole touchpad area very rapidly.
> 6. Observe that Emacs doesn't scroll almost at all and just waits until
>    scroll events will stop.  Then it scrolls correct amount.
> 
> The delay I'm talking about is what bothers me.

I cannot reproduce this.  Did you try "emacs -Q"?

Please load mwheel.el (NOT the .elc file!), and then profile the slow
scrolling again and show a fully-expanded profile.  That might help us
understand what part of mwheel-scroll takes the lion's share of CPU
cycles.





  reply	other threads:[~2021-02-06 17:59 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-06 17:33 bug#46350: 28.0.50; touchpad-scrolling-eats-lots-of-cpu-samples Andrey Orst
2021-02-06 17:59 ` Eli Zaretskii [this message]
2021-02-06 18:34   ` Andrey Orst
2021-02-06 18:55     ` Andrey Orst
2021-02-06 19:05       ` Eli Zaretskii
2021-02-06 19:02     ` Eli Zaretskii
2021-02-06 19:47       ` Andrey Orst
2021-02-06 20:03         ` Eli Zaretskii
2021-02-07 17:23           ` Andrey Orst
2021-02-07 17:49             ` Eli Zaretskii
2021-02-07 18:33               ` Andrey Orst
2021-02-07 18:44                 ` Eli Zaretskii
2021-02-07 18:52                   ` Andrey Orst
2021-02-07 19:05                     ` Eli Zaretskii
2021-02-07 19:37                       ` Lars Ingebrigtsen
2021-02-07 19:47                         ` Eli Zaretskii
2021-02-07 20:54                           ` Lars Ingebrigtsen
2021-02-07 22:16                     ` Alan Third
2021-02-07 22:22                       ` Andrey Orst
2021-02-07 22:24                         ` Alan Third
2021-02-07 22:30                           ` Andrey Orst
2021-02-08 10:12                             ` Andrey Orst
2021-02-08 14:35                               ` Andrey Orst
2021-02-08 15:28                                 ` Eli Zaretskii
2021-02-08 15:31                                   ` Andrey Orst
2021-02-08 15:19                               ` 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=83a6shnklg.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=46350@debbugs.gnu.org \
    --cc=andreyorst@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).