all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: help-gnu-emacs@gnu.org
Subject: Re: Performance problems (CPU 100%) with NULs in files
Date: Thu, 22 Sep 2011 01:44:37 -0400	[thread overview]
Message-ID: <E1R6c5N-0007s4-N6@fencepost.gnu.org> (raw)
In-Reply-To: <BC5672F8AD4C054BAF167C9801500D1A510C1869@USSLMMBX003.net.plm.eds.com> (ludwig.mark@siemens.com)

> From: "Ludwig, Mark" <ludwig.mark@siemens.com>
> Thread-Topic: Performance problems (CPU 100%) with NULs in files
> Date: Wed, 21 Sep 2011 21:08:42 +0000
> 
> What happens is that as I scroll through the file, when the NULs are visible, Emacs gets into some intensive processing for a long time (minutes, sometimes!).  It eventually unwinds and repaints the display, but any movement of point sends it into this loop again.  I have found that M-< or M-> will quickly reposition away from the problem (assuming the beginning and/or end of the file do not contain NULs).  Most other movement operations send it into the loop.

Does it help to visit such files without code conversions, i.e.

  M-x find-file-literally RET FILENAME RET

?

If not, please file a bug report and attach to it an example file that
causes this slowdown.



  parent reply	other threads:[~2011-09-22  5:44 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-09-21 21:08 Performance problems (CPU 100%) with NULs in files Ludwig, Mark
2011-09-22  4:30 ` Drew Adams
2011-09-22 13:00   ` Ludwig, Mark
2011-09-22  5:44 ` Eli Zaretskii [this message]
2011-09-22 12:58   ` Ludwig, Mark
2011-09-24  0:20   ` Ludwig, Mark
2011-09-24  0:50     ` Le Wang
2011-09-24  6:04     ` Eli Zaretskii
2011-09-24 13:32       ` Ludwig, Mark
2011-09-24 14:15         ` Eli Zaretskii
2011-09-22  6:09 ` XeCycle
2011-09-22 12:58   ` Ludwig, Mark

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=E1R6c5N-0007s4-N6@fencepost.gnu.org \
    --to=eliz@gnu.org \
    --cc=help-gnu-emacs@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.