emacs-bug-tracker
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[debbugs-tracker] bug#24565: closed (25.1: info freezes on some elements


From: GNU bug Tracking System
Subject: [debbugs-tracker] bug#24565: closed (25.1: info freezes on some elements)
Date: Sat, 08 Oct 2016 19:39:02 +0000

Your message dated Sat, 08 Oct 2016 22:37:55 +0300
with message-id <address@hidden>
and subject line Re: bug#24565: 25.1: info freezes on some elements
has caused the debbugs.gnu.org bug report #24565,
regarding 25.1: info freezes on some elements
to be marked as done.

(If you believe you have received this mail in error, please contact
address@hidden)


-- 
24565: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=24565
GNU Bug Tracking System
Contact address@hidden with problems
--- Begin Message --- Subject: 25.1: info freezes on some elements Date: Thu, 29 Sep 2016 10:30:26 +0300 User-agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.3.0
1. emacs -Q
2. (info "(elisp) Association Lists")
3. Hold down next-line.

What should happen: the moment you see the arrow symbol in some examples, you should get a freeze for a couple of seconds. Sexps in the beggining of that page, without the arrow do not seem to trigger the freeze. It also seems like those freezes are accumulative - that is freeze for a page with three arrows is three times as long as a freeze for a single arrow.

Happens on Windows.

This bug happens both on master and 25.1, with official binaries. This does not happen in 24.5.

--
Best Regards,
Nikolay Kudryavtsev




--- End Message ---
--- Begin Message --- Subject: Re: bug#24565: 25.1: info freezes on some elements Date: Sat, 08 Oct 2016 22:37:55 +0300
> Date: Sat, 01 Oct 2016 12:48:40 +0300
> From: Eli Zaretskii <address@hidden>
> Cc: address@hidden
> 
> > The discussion about #15876 ended with your suggestion to comment
> > that stuff out just for that bug.
> 
> That was before the serious problems I mentioned previously were
> fixed.

I've now added a variable that can be used to disable the cache
compaction.  See the discussion of bug#24634.

With this, I consider this bug done.

Thanks.


--- End Message ---

reply via email to

[Prev in Thread] Current Thread [Next in Thread]