From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: unfrostedpoptart Newsgroups: gmane.emacs.help Subject: help! Keep getting emacs locked up / not responding to c-g / having to kill process Date: Wed, 2 Oct 2013 21:53:01 -0700 (PDT) Message-ID: NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable X-Trace: ger.gmane.org 1380776113 27827 80.91.229.3 (3 Oct 2013 04:55:13 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Thu, 3 Oct 2013 04:55:13 +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 Oct 03 06:55:18 2013 Return-path: Envelope-to: geh-help-gnu-emacs@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 1VRawX-0006hX-SV for geh-help-gnu-emacs@m.gmane.org; Thu, 03 Oct 2013 06:55:17 +0200 Original-Received: from localhost ([::1]:39833 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1VRawX-0005rD-JT for geh-help-gnu-emacs@m.gmane.org; Thu, 03 Oct 2013 00:55:17 -0400 X-Received: by 10.224.5.5 with SMTP id 5mr10383490qat.4.1380775981393; Wed, 02 Oct 2013 21:53:01 -0700 (PDT) X-Received: by 10.49.24.132 with SMTP id u4mr414qef.17.1380775981342; Wed, 02 Oct 2013 21:53:01 -0700 (PDT) Original-Path: usenet.stanford.edu!a6no2260814qak.0!news-out.google.com!9ni4992qaf.0!nntp.google.com!q9no2555142qas.0!postnews.google.com!glegroupsg2000goo.googlegroups.com!not-for-mail Original-Newsgroups: gnu.emacs.help Complaints-To: groups-abuse@google.com Injection-Info: glegroupsg2000goo.googlegroups.com; posting-host=68.99.177.206; posting-account=S61AnQkAAADt4_PSYpI-Tm-z1E4cd7xa Original-NNTP-Posting-Host: 68.99.177.206 User-Agent: G2/1.0 Injection-Date: Thu, 03 Oct 2013 04:53:01 +0000 Original-Xref: usenet.stanford.edu gnu.emacs.help:201535 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:93805 Archived-At: This is related to my previous post about clearing the kill ring. I have a= frequent case, when running shell buffers, where selecting a lot of the bu= ffer (could be thousands of lines) seems to lock up emacs. Most of the tim= e, one or more c-g hits will stop what it was doing and give me back contro= l. However, lately (including 15 minutes ago) I've been hitting this and c= -g does nothing and ps shows emacs at around 95% cpu. As this is a shared = server, that doesn't make me popular with other users! I end up having to kill the process. This really sucks since I had about a = dozen shell buffers logged into multiple servers and running long jobs tha= t were all killed when I killed emacs. Any suggestions on stopping this from happening in the first place and/or s= omething stronger than c-g but short of killing emacs? FYI, this is 24.3.something on REH 5.something. Thanks! David