[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: master e1e0315252 01/14: Initial implementation of "abort-redisplay"
From: |
Eli Zaretskii |
Subject: |
Re: master e1e0315252 01/14: Initial implementation of "abort-redisplay" feature |
Date: |
Fri, 24 Jun 2022 16:36:28 +0300 |
> From: Lars Ingebrigtsen <larsi@gnus.org>
> Cc: emacs-diffs@gnu.org
> Date: Fri, 24 Jun 2022 15:11:26 +0200
>
> Eli Zaretskii <eliz@gnu.org> writes:
>
> > I cannot reproduce this. Does it happen with the latest master? If
> > so, can you put a breakpoint in xdisp.c here:
> >
> > if (w && w->desired_matrix)
> > w->desired_matrix->no_scrolling_p = true;
> > error ("Window showing buffer %s takes too long to redisplay",
> > bufname);
> >
> > on the line that calls 'error', and when it breaks, show the
> > backtrace, both the C backtrace and Lisp backtrace?
>
> Hm. I seem to be unable to reproduce it reliably. I wondered whether
> having a whole bunch of animated images would trigger it more often, so
> I tried with this:
>
> http://quimby.gnus.org/s/many-anim.html
>
> But no, no warning -- unless I scroll down, and then up a bit, and then
> a bit down again. Sometimes.
Doesn't happen with that as well. So if you can show the backtrace I
asked for, it might help.
- master updated (fbb703f60a -> 289b457cac), Eli Zaretskii, 2022/06/24
- master e1e0315252 01/14: Initial implementation of "abort-redisplay" feature, Eli Zaretskii, 2022/06/24
- Re: master e1e0315252 01/14: Initial implementation of "abort-redisplay" feature, Lars Ingebrigtsen, 2022/06/24
- Re: master e1e0315252 01/14: Initial implementation of "abort-redisplay" feature, Eli Zaretskii, 2022/06/24
- Re: master e1e0315252 01/14: Initial implementation of "abort-redisplay" feature, Lars Ingebrigtsen, 2022/06/24
- Re: master e1e0315252 01/14: Initial implementation of "abort-redisplay" feature, Eli Zaretskii, 2022/06/24
- Re: master e1e0315252 01/14: Initial implementation of "abort-redisplay" feature, Lars Ingebrigtsen, 2022/06/24
- Re: master e1e0315252 01/14: Initial implementation of "abort-redisplay" feature,
Eli Zaretskii <=
- Re: master e1e0315252 01/14: Initial implementation of "abort-redisplay" feature, Lars Ingebrigtsen, 2022/06/24
master f1e1392868 03/14: Change the API of 'update_redisplay_ticks', Eli Zaretskii, 2022/06/24
master 82626e62ab 08/14: Allow aborting redisplay stuck in 'parse-partial-sexp', Eli Zaretskii, 2022/06/24
master a82af5ae78 09/14: Don't count ticks too eagerly in syntax.c, Eli Zaretskii, 2022/06/24
master 5a596bbed5 02/14: Fix a typo in a doc string., Eli Zaretskii, 2022/06/24
master bd44f39d6d 04/14: Restart tick counting every command, Eli Zaretskii, 2022/06/24
master 264472a507 05/14: Handle W = NULL in 'update_redisplay_ticks', Eli Zaretskii, 2022/06/24
master b89b23079c 12/14: Show warnings about aborted redisplay, Eli Zaretskii, 2022/06/24
master 287e714fe0 11/14: Update redisplay ticks for more operations, and misc modifications, Eli Zaretskii, 2022/06/24
master 94e1185369 06/14: Support callers which sometimes run unrelated to display code, Eli Zaretskii, 2022/06/24