From mboxrd@z Thu Jan 1 00:00:00 1970 From: Nick Dokos Subject: Re: Emacs hangs in org file Date: Mon, 07 Jan 2013 08:41:01 -0500 Message-ID: <7065.1357566061@alphaville> References: Reply-To: nicholas.dokos@hp.com Return-path: Received: from eggs.gnu.org ([208.118.235.92]:43939) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1TsCx0-0000b7-8G for emacs-orgmode@gnu.org; Mon, 07 Jan 2013 08:41:16 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1TsCwv-0008F1-Fq for emacs-orgmode@gnu.org; Mon, 07 Jan 2013 08:41:14 -0500 Received: from g6t0185.atlanta.hp.com ([15.193.32.62]:3362) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1TsCwv-0008E4-Bl for emacs-orgmode@gnu.org; Mon, 07 Jan 2013 08:41:09 -0500 In-Reply-To: Message from Stelian Iancu of "Mon, 07 Jan 2013 09:21:40 +0100." List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: Stelian Iancu Cc: emacs-orgmode@gnu.org Stelian Iancu wrote: > I have a fairly simple org file with only a couple of headings, TODOs > and some notes. The issue I'm seeing is that Emacs hangs to the point > where I have to force close it when I'm trying to expand a > headline. The behavior seems random, i.e. it's not always the same > header and I don't have specific steps to reproduce. > > Versions: > GNU Emacs 24.3.50.1 (x86_64-apple-darwin, NS apple-appkit-1038.36) of 2012-12-30 on bob.porkrind.org > > Org-mode version 7.9.2 (7.9.2-181-ge8aaca-elpaplus @ /Users/stelianiancu/.emacs.d/elpa/ > org-plus-contrib-20121231/) > > Any ideas how can I debug this further or why this might happen? > Does it hang or is is stuck in a loop? Check whether emacs is is accumulating CPU time with ps. If it's in a loop and C-g works to get it out, you can set debug-on-quit, interrupt it and ponder the backtrace. Doing it a couple of times might indicate where the problem is. If not, then the only thing I can think of is attaching strace to the emacs process, and figuring out what it is doing. In either case, easier said than done, but desperate times call for desperate measures. Nick