GNU bug report logs - #19776
25.0.50; HTML rendering is very slow

Previous Next

Package: emacs;

Reported by: rms <at> gnu.org

Date: Wed, 4 Feb 2015 23:04:02 UTC

Severity: minor

Merged with 22846

Found in versions 25.0.50, 25.0.91

Fixed in version 29.1

Done: Lars Ingebrigtsen <larsi <at> gnus.org>

Bug is archived. No further changes may be made.

Full log


View this message in rfc822 format

From: Eli Zaretskii <eliz <at> gnu.org>
To: Stefan Kangas <stefan <at> marxist.se>
Cc: larsi <at> gnus.org, rms <at> gnu.org, 19776 <at> debbugs.gnu.org
Subject: bug#19776: 25.0.50; HTML rendering is very slow
Date: Sat, 23 Oct 2021 10:27:51 +0300
> From: Stefan Kangas <stefan <at> marxist.se>
> Date: Fri, 22 Oct 2021 16:59:55 -0700
> Cc: Richard Stallman <rms <at> gnu.org>, 19776 <at> debbugs.gnu.org
> 
> >> then we'd be able to display a message if the code took longer than 1
> >> second.  We don't have that, do we?
> >
> > Oh, I asked this before, and the answer is "nope, not at all".
> >
> > The problem is that it can't be done with normal timers, since "all the
> > code" may be pure Elisp and never yield.  For that reason, it can't be
> > done with the new thread support, either.
> >
> > So it would require some C-level magic.
> 
> I guess we can't do this for the C-level DEFUN's (without massive
> changes), but we might be able to check some timer before executing a
> Lisp function or something.  However, wouldn't such a new check risk
> slowing Emacs down as a whole?

Did someone consider using atimers for this purpose?  See atimer.c.




This bug report was last modified 3 years and 206 days ago.

Previous Next


GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.