unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Ravine Var <ravine.var@gmail.com>
To: Alan Mackenzie <acm@muc.de>
Cc: 45248@debbugs.gnu.org
Subject: bug#45248: 28.0.50; Emacs freezes with big C functions
Date: Sat, 19 Dec 2020 09:58:48 +0530	[thread overview]
Message-ID: <87pn36o1le.fsf@gmail.com> (raw)
In-Reply-To: <X9zm6KO1BVRc4uxC@ACM>

Alan Mackenzie <acm@muc.de> writes:
> Let's be clear about the situation: CC Mode does just too much
> processing in refontification for current hardware to be able to scroll
> smoothly through a buffer at normal auto-repeat speeds.  Setting
> fast-but-imprecise-scrolling to non-nil is a handy workaround, but it
> isn't good enough to make the scrolling appear to be smooth when one
> holds down C-v.  I think (and hope) this is what you mean by
> "stuttering".

Yes, that's what I meant. These are my keyboard settings:

$ xset q | grep "repeat rate"
  auto repeat delay:  200    repeat rate:  30

> The bug which I'm hoping to have fixed was that in the large struct in
> Wireshark's function proto_register_rrc, the scrolling got slower and
> slower as one got further into the struct.  On my machine, 80% of the
> way through that struct, scrolling a single screen (62 lines) was taking
> between four and five seconds, which was unacceptably slow.  With the
> bug fix, this scrolling takes about 75 milliseconds, regardless of the
> position in the struct.  This is apart from the first screen drawing in
> the neighbourhood, which takes a little time to fill the new cache
> entry.
>
> Could you please confirm that you see the same uniformity in scrolling
> speed anywhere inside a large struct, and that the speed is acceptably
> close to instantaneous for a single scrolling operation.  Or do you see
> something different?  Thanks!

I still see the behavior that you have described. With the patch,
scrolling becomes slower and slower rapidly and the screen locks up
(using emacs -Q). I tested with a single C file containing just
the function proto_register_rrc().





  reply	other threads:[~2020-12-19  4:28 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-15  3:59 bug#45248: 28.0.50; Emacs freezes with big C functions Ravine Var
2020-12-15 16:05 ` Eli Zaretskii
2020-12-17 15:08 ` Alan Mackenzie
2020-12-18 11:17   ` Ravine Var
2020-12-18 17:29     ` Alan Mackenzie
2020-12-19  4:28       ` Ravine Var [this message]
2020-12-22 20:40         ` Alan Mackenzie
2020-12-23  3:18           ` Ravine Var
2020-12-24 11:50             ` Alan Mackenzie

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=87pn36o1le.fsf@gmail.com \
    --to=ravine.var@gmail.com \
    --cc=45248@debbugs.gnu.org \
    --cc=acm@muc.de \
    /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).