GNU bug report logs - #38407
27.0.50; infinite loop with display of large file without newlines

Previous Next

Package: emacs;

Reported by: Pieter van Oostrum <pieter <at> vanoostrum.org>

Date: Wed, 27 Nov 2019 22:07:01 UTC

Severity: normal

Found in version 27.0.50

Full log


View this message in rfc822 format

From: Eli Zaretskii <eliz <at> gnu.org>
To: Pieter van Oostrum <pieter <at> vanoostrum.org>
Cc: psainty <at> orcon.net.nz, 38407 <at> debbugs.gnu.org
Subject: bug#38407: 27.0.50; infinite loop with display of large file without newlines
Date: Mon, 02 Dec 2019 18:23:41 +0200
> Date: Sun, 1 Dec 2019 17:35:35 +0100
> From: Pieter van Oostrum <pieter <at> vanoostrum.org>
> Cc: 38407 <at> debbugs.gnu.org
> 
> Opened this version of Emacs. 
> (setq bidi-inhibit-bpa t)
> open the file extensions.json (i.e. without visual-line-mode)
> go to the end of the buffer.
> Emacs gets responsive again after about one minute.
> Then I open a new frame (Cmd-N), the frame appears, so this proves that Emacs was responsive.
> But after opening the frame, Emacs is unresponsive again with 100% CPU usage. After 30 minutes, I killed it.

When more than one frame is displayed, some redisplay cycles redraw
more than just the selected frame.  If you don't want the frame with
the "problematic" buffer ti get in the way, minimize it.

Although I don't understand why you see 30 minutes and longer delays,
you should see the same 1 minute as on the original frame.




This bug report was last modified 5 years and 192 days ago.

Previous Next


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