From mboxrd@z Thu Jan 1 00:00:00 1970 From: Nick Dokos Subject: Re: Generating agenda endless-loop Date: Sat, 02 Aug 2014 09:33:27 -0400 Message-ID: <87silf8194.fsf@gmail.com> References: <2014-08-02T11-30-07@devnull.Karl-Voit.at> Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:50093) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1XDZRW-0004gb-UP for emacs-orgmode@gnu.org; Sat, 02 Aug 2014 09:33:56 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1XDZRR-0005rH-1T for emacs-orgmode@gnu.org; Sat, 02 Aug 2014 09:33:50 -0400 Received: from plane.gmane.org ([80.91.229.3]:35223) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1XDZRQ-0005r4-R8 for emacs-orgmode@gnu.org; Sat, 02 Aug 2014 09:33:44 -0400 Received: from list by plane.gmane.org with local (Exim 4.69) (envelope-from ) id 1XDZRP-0001YJ-7p for emacs-orgmode@gnu.org; Sat, 02 Aug 2014 15:33:43 +0200 Received: from pool-173-48-174-104.bstnma.fios.verizon.net ([173.48.174.104]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Sat, 02 Aug 2014 15:33:43 +0200 Received: from ndokos by pool-173-48-174-104.bstnma.fios.verizon.net with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Sat, 02 Aug 2014 15:33:43 +0200 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: emacs-orgmode@gnu.org Karl Voit writes: > My agenda generally works. However, sometimes, by working with Emacs > I get to the "status" where I can not re-generate the agenda: it is > in an endless loop with 100% of its Emacs-CPU-core. I can quit by > pressing M-g. After re-starting Emacs, it works again without > modifying my Org-files or the Emacs configuration. > > Here is a profiler CPU report after I quit the endless loop for > about a minute or so: > > ... > > Do you have any suggestion how I can check this out any further or > get rid of this behavior? > It might be useful to M-x toggle-debug-on-error and try the agenda command again: if it gets stuck in the loop again, a C-g will produce a backtrace that might shed some light. -- Nick