From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: unfrostedpoptart Newsgroups: gmane.emacs.help Subject: Re: help! Keep getting emacs locked up / not responding to c-g / having to kill process Date: Thu, 3 Oct 2013 09:54:25 -0700 (PDT) Message-ID: <83750ce8-19b7-4a13-9a66-6426fd28b082@googlegroups.com> References: 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 1380819315 527 80.91.229.3 (3 Oct 2013 16:55:15 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Thu, 3 Oct 2013 16:55:15 +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 18:55:19 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 1VRmBK-0006Le-OB for geh-help-gnu-emacs@m.gmane.org; Thu, 03 Oct 2013 18:55:18 +0200 Original-Received: from localhost ([::1]:44336 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1VRmBK-0002D6-AQ for geh-help-gnu-emacs@m.gmane.org; Thu, 03 Oct 2013 12:55:18 -0400 X-Received: by 10.224.2.68 with SMTP id 4mr15792438qai.1.1380819266233; Thu, 03 Oct 2013 09:54:26 -0700 (PDT) X-Received: by 10.49.99.37 with SMTP id en5mr313496qeb.8.1380819266208; Thu, 03 Oct 2013 09:54:26 -0700 (PDT) Original-Path: usenet.stanford.edu!q9no3309548qas.0!news-out.google.com!9ni4233qaf.0!nntp.google.com!a6no3005453qak.0!postnews.google.com!glegroupsg2000goo.googlegroups.com!not-for-mail Original-Newsgroups: gnu.emacs.help In-Reply-To: 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 16:54:26 +0000 Original-Xref: usenet.stanford.edu gnu.emacs.help:201547 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:93817 Archived-At: On Thursday, October 3, 2013 8:44:22 AM UTC-7, Michael Heerdegen wrote: > unfrostedpoptart writes: > > 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! >=20 > As Drew mentioned, it's hard to guess who the culprit is without more det= ails (recipe). > Anyway, in Unices you can force Emacs into the debugger, even if not > responsive, by sending SIGUSR2: >=20 > pkill -SIGUSR2 emacs > Using the debugger, you hopefully should be able to see where Emacs loops= . Thanks guys! I ran kill -l to look for something like Michael just suggest= ed but didn't know what the different signals meant. I'll try this. Also, I'll try a big cleanup of my init.el. It's been evolving for over 20= years since 18.57! Every new emacs release, I try and clean it up some fo= r deprecated functions and code that's not needed anymore because of new, b= uilt-in functions. I know I have a lot of ugly stuff related to shell-mode= and I'l see if I can remove most of it. David