all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "Óscar Fuentes" <ofv@wanadoo.es>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 22739@debbugs.gnu.org
Subject: bug#22739: 25.0.50; Hangs on revertig buffer
Date: Sun, 06 Mar 2016 02:28:29 +0100	[thread overview]
Message-ID: <8737s48kea.fsf@wanadoo.es> (raw)
In-Reply-To: <87h9h4dg3q.fsf@wanadoo.es> ("Óscar Fuentes"'s message of "Fri, 19 Feb 2016 13:44:41 +0100")

It happened again, but this time the file was corrupt and contained 230
KB of garbage (all nulls except for the last few characters, which are
ASCII.)

The infloop was on bidi functions and it was necessary to SIGKILL the
process. SIGINT didn't work.

It is repeatable with emacs -Q.

In GNU/Linux you can create a file full of nulls with

$ truncate -s 100000 kk
$ emacs -Q kk

It seems that it is some type of quadratic (or worse) time complexity
with long lines, because with smaller sizes (100, 1000, ...) Emacs comes
back.

So it is the old problem with very long lines. We should try to bail out
when processing this type of lines takes too much time. From certain
point, simply refusing to display the line (or the entire file) is
preferable to freezing Emacs.





  parent reply	other threads:[~2016-03-06  1:28 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-19  3:33 bug#22739: 25.0.50; Hangs on revertig buffer Óscar Fuentes
2016-02-19  8:16 ` Eli Zaretskii
2016-02-19 12:44   ` Óscar Fuentes
2016-02-19 15:28     ` Eli Zaretskii
2016-03-06  1:28     ` Óscar Fuentes [this message]
2016-03-06  3:41       ` Eli Zaretskii
2016-03-06  4:39         ` Óscar Fuentes
2016-03-06 16:22           ` Eli Zaretskii
2016-03-07  0:29             ` Óscar Fuentes
2016-03-07 16:32               ` Eli Zaretskii
2016-02-19 13:04   ` Óscar Fuentes
2016-02-19 13:21   ` Óscar Fuentes
2016-02-19 15:45     ` Eli Zaretskii
2016-02-19 22:09       ` Óscar Fuentes
2016-02-20  8:08         ` Eli Zaretskii
2016-02-20 16:40           ` Óscar Fuentes

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=8737s48kea.fsf@wanadoo.es \
    --to=ofv@wanadoo.es \
    --cc=22739@debbugs.gnu.org \
    --cc=eliz@gnu.org \
    /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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.