From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Jorgen Schaefer Newsgroups: gmane.emacs.devel Subject: Strange Emacs "hiccup" bug Date: Sat, 10 May 2014 22:13:51 +0200 Message-ID: <20140510221351.31049497@forcix.jorgenschaefer.de> NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Trace: ger.gmane.org 1399752893 15130 80.91.229.3 (10 May 2014 20:14:53 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Sat, 10 May 2014 20:14:53 +0000 (UTC) To: emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Sat May 10 22:14:46 2014 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by plane.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1WjDfQ-00089q-73 for ged-emacs-devel@m.gmane.org; Sat, 10 May 2014 22:14:44 +0200 Original-Received: from localhost ([::1]:58833 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1WjDfP-00084s-LN for ged-emacs-devel@m.gmane.org; Sat, 10 May 2014 16:14:43 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:52045) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1WjDfF-0007yv-8E for emacs-devel@gnu.org; Sat, 10 May 2014 16:14:40 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1WjDf7-0005QR-PU for emacs-devel@gnu.org; Sat, 10 May 2014 16:14:33 -0400 Original-Received: from loki.jorgenschaefer.de ([87.230.15.51]:43173) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1WjDf7-0005QA-Ic for emacs-devel@gnu.org; Sat, 10 May 2014 16:14:25 -0400 Original-Received: by loki.jorgenschaefer.de (Postfix, from userid 998) id DB514201FA1; Sat, 10 May 2014 22:13:52 +0200 (CEST) Original-Received: from forcix.jorgenschaefer.de (port-6483.pppoe.wtnet.de [84.46.25.108]) by loki.jorgenschaefer.de (Postfix) with ESMTPSA id 81452201F9F for ; Sat, 10 May 2014 22:13:52 +0200 (CEST) X-Mailer: Claws Mail 3.9.3 (GTK+ 2.24.23; i486-pc-linux-gnu) X-detected-operating-system: by eggs.gnu.org: GNU/Linux 3.x X-Received-From: 87.230.15.51 X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:171795 Archived-At: Hello! I am trying to debug a problem I have encountered a few times now, but I'm at a loss as to what to do next to figure out what is happening. Maybe someone here has an idea. I have witnessed this bug, or at least one that looks *very much* like this, a number of times over the last months. I have re-built Emacs a few times in between. The current build is from trunk on 2014-05-01. At some point, apparently after some time of continuous use, Emacs starts to pause intermittently. It stops responding to keys or redisplaying for half a second, then it goes on. It does not matter which mode or buffer is in use. In this particular case, after a few attempts to figure out what's going on with no effect, I simply killed all buffers. The behavior continued, even in *Messages*. A look at the process list showed a bunch of zombie processes around: 15361 ? Ss 0:33 SCREEN 15362 pts/1 Ss 0:00 \_ /bin/bash 18175 pts/1 R+ 37:06 | \_ emacs 18206 ? Zs 0:00 | \_ [openssl] 23385 ? Zs 0:04 | \_ [openssl] 24238 ? Zs 0:00 | \_ [aspell] 24999 ? Zs 0:00 | \_ [aspell] 28117 ? Zs 0:00 | \_ [bash] 18706 ? Zs 0:00 | \_ [python] 20096 ? Zs 0:00 | \_ [python] A strace -fttT showed a very fast loop doing this: 21:24:00.948071 pselect6(12, [3 4 9 11], [], NULL, {0, 1376013}, {NULL, 8}) = 2 (in [9 11], left {0, 1373467}) <0.000011> 21:24:00.948529 read(9, "", 4096) = 0 <0.000009> 21:24:00.948564 read(11, "", 4096) = 0 <0.000008> It turned out 9 and 11 were two pipes to openssl. Emacs still had three processes active: The emacsclient server and two openssl connections. Even though both openssl connections had died. Deleting the processes in Emacs improved responsiveness somewhat, but did not completely remove the "hiccups". The strace behavior returned to normal, though. A M-x toggle-debug-on-quit and some lucky C-g's got me the following: Error during redisplay: (#[128 "\300\301^B\"\210\300\302^B\"\207" [apply redisplay--update-region-highlights ignore nil] 4 nil nil] nil) signaled (quit) But I'm not sure if that is really related, or if it just happened to be what Emacs was evaluating at that time. Now I'm stuck. Any ideas what I can do to debug this further? Regards, Jorgen