From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: "Ludwig, Mark" Newsgroups: gmane.emacs.help Subject: RE: Performance problems (CPU 100%) with NULs in files Date: Thu, 22 Sep 2011 12:58:18 +0000 Message-ID: References: NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable X-Trace: dough.gmane.org 1316696340 24456 80.91.229.12 (22 Sep 2011 12:59:00 GMT) X-Complaints-To: usenet@dough.gmane.org NNTP-Posting-Date: Thu, 22 Sep 2011 12:59:00 +0000 (UTC) To: "help-gnu-emacs@gnu.org" Original-X-From: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Thu Sep 22 14:58:56 2011 Return-path: Envelope-to: geh-help-gnu-emacs@m.gmane.org Original-Received: from lists.gnu.org ([140.186.70.17]) by lo.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1R6irg-0007dg-0a for geh-help-gnu-emacs@m.gmane.org; Thu, 22 Sep 2011 14:58:56 +0200 Original-Received: from localhost ([::1]:40728 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1R6irf-0001Ny-L5 for geh-help-gnu-emacs@m.gmane.org; Thu, 22 Sep 2011 08:58:55 -0400 Original-Received: from eggs.gnu.org ([140.186.70.92]:35575) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1R6irT-0000zu-Vk for help-gnu-emacs@gnu.org; Thu, 22 Sep 2011 08:58:45 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1R6irP-0007ap-CD for help-gnu-emacs@gnu.org; Thu, 22 Sep 2011 08:58:43 -0400 Original-Received: from usslmhub002.ugs.com ([134.244.32.85]:29496 helo=ugs.com) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1R6irP-0007Za-9A for help-gnu-emacs@gnu.org; Thu, 22 Sep 2011 08:58:39 -0400 Original-Received: from USSLMMBX002.net.plm.eds.com (161.134.138.62) by USSLMHUB002.net.plm.eds.com (134.244.32.85) with Microsoft SMTP Server (TLS) id 14.1.323.3; Thu, 22 Sep 2011 07:58:19 -0500 Original-Received: from USSLMMBX003.net.plm.eds.com ([169.254.2.147]) by USSLMMBX002.net.plm.eds.com ([169.254.1.150]) with mapi id 14.01.0323.003; Thu, 22 Sep 2011 07:58:18 -0500 Thread-Topic: Performance problems (CPU 100%) with NULs in files Thread-Index: Acx4opaN4QXNwclhR/W8cESA6FxoywASCq0SAA7hgjA= In-Reply-To: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [146.122.220.190] X-detected-operating-system: by eggs.gnu.org: Windows 2000 SP2+, XP SP1+ (seldom 98) X-Received-From: 134.244.32.85 X-BeenThere: help-gnu-emacs@gnu.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Users list for the GNU Emacs text editor List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Original-Sender: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.help:82292 Archived-At: > From: Eli Zaretskii > Subject: Re: Performance problems (CPU 100%) with NULs in files >=20 > > From: "Ludwig, Mark" > > 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. >=20 > Does it help to visit such files without code conversions, i.e. >=20 > M-x find-file-literally RET FILENAME RET >=20 > ? No, it doesn't, but when doing this, I noticed that something else that hap= pens is that the displayed line number changes to "??" when point gets into= the NULs. I turned off line-number-mode, but that had no effect either. = (I could imagine the code would waste a lot of time looking for end-of-line= characters in those NULs....) > If not, please file a bug report and attach to it an example file that > causes this slowdown. As soon as I get a minimal test case that shows the problem, I will. Thanks, Mark