unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Andrey Orst <andreyorst@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 46350@debbugs.gnu.org
Subject: bug#46350: 28.0.50; touchpad-scrolling-eats-lots-of-cpu-samples
Date: Sat, 6 Feb 2021 22:47:55 +0300	[thread overview]
Message-ID: <CAAKhXobsjNokSNLo5GeJoFW+9WPkiAH5vw1nKrk3O8LSsZbtdw@mail.gmail.com> (raw)
In-Reply-To: <838s81nhoz.fsf@gnu.org>

[-- Attachment #1: Type: text/plain, Size: 956 bytes --]

>
> Do you use a large frame and/or a small
> font?


In fact, yes, my screen is 2K, and system font scaling is set to 1.44, but
this also happens on regular 1080p screen with regularly sized font.

And how many mouse-wheel events Emacs receives in your
> scenario, anyway?
>

Sorry, how can I check that? I do think that Emacs actually receives a
metric ton of events, as scolling with mouse seems hardly lag at all, and
scrolling in termux with touch events also not as laggy.

Oh, and what happens if you raise gc-cons-threshold to a large value?
>

No difference. Note, that scrolling with scrollbars has no lag at all, so I
don't think that GC is relevant here.

I've also noticed that scrollin with scrollbar has (sit-for 0) in the body
of the scroll function, and IIRC mwheel-scroll doesnt sit at all. maybe
because of that it consumes too many inputs?

I wonder if you could send tons of scrolling inputs via xdotool or smth
like that on Linux?

>

[-- Attachment #2: Type: text/html, Size: 3135 bytes --]

  reply	other threads:[~2021-02-06 19:47 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
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 [this message]
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=CAAKhXobsjNokSNLo5GeJoFW+9WPkiAH5vw1nKrk3O8LSsZbtdw@mail.gmail.com \
    --to=andreyorst@gmail.com \
    --cc=46350@debbugs.gnu.org \
    --cc=eliz@gnu.org \
    /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).