From mboxrd@z Thu Jan 1 00:00:00 1970 From: Daimrod Subject: Re: still seeing semi-regular lockups Date: Wed, 25 Jun 2014 16:38:30 +0900 Message-ID: <877g45jv61.fsf@tanger.home> References: <87siocrbyb.fsf@ericabrahamsen.net> <87siobtn1i.fsf@bzg.ath.cx> <87ha4r1j91.fsf@tanger.home> <87k39hdf2o.fsf@tanger.home> <87ppj86elt.fsf@ericabrahamsen.net> <874n0kde2y.fsf@tanger.home> <87bnus4s5n.fsf@ericabrahamsen.net> <87egye7kx3.fsf@nicolasgoaziou.fr> <87a992mleu.fsf@ericabrahamsen.net> <87mwd1hbpx.fsf@fastmail.fm> Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:37124) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Wzhmz-0006jl-Uu for emacs-orgmode@gnu.org; Wed, 25 Jun 2014 03:38:46 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1Wzhmu-0000Bc-Pt for emacs-orgmode@gnu.org; Wed, 25 Jun 2014 03:38:41 -0400 Received: from mail-pa0-x22a.google.com ([2607:f8b0:400e:c03::22a]:34699) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Wzhmu-0000BA-Ji for emacs-orgmode@gnu.org; Wed, 25 Jun 2014 03:38:36 -0400 Received: by mail-pa0-f42.google.com with SMTP id lj1so1374562pab.29 for ; Wed, 25 Jun 2014 00:38:35 -0700 (PDT) In-Reply-To: <87mwd1hbpx.fsf@fastmail.fm> (Matt Lundin's message of "Tue, 24 Jun 2014 23:09:14 -0500") 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: Matt Lundin Cc: emacs-orgmode@gnu.org Matt Lundin writes: > Eric Abrahamsen writes: > >> Nicolas Goaziou writes: >> >>> Hello, >>> >>> Eric Abrahamsen writes: >>> >>>> None of those three, I'm afraid! It was hanging on a variety of editing >>>> operations that, as far as I can tell, had little in common. There's a >>>> possibility that they were list-item-related, but really there wasn't >>>> much commonality. >>> >>> FYI, I recently fixed a bug[fn:1] that could introduce uncommon random >>> lockups. Hopefully, it may be related to your problem (which is >>> different from Daimrod's). >> >> Thanks for the followup! I was watching Daimrod's thread, and also >> Matt's most recent posting -- that also seemed more relevant to my >> problems, which were almost solely confined to log/state notes. I've >> pulled the fix, and will let you know if I see any more problems. > > With the latest git, I've experienced three lock-ups/freezes this > evening when a) archiving a subtree to a file, b) changing a todo state > with repeating timestamp, and 3) calling C-c C-c in an org-capture > buffer. (I don't think this is due to a recent change - I've been > running into these lockups sporadically for several months.) > > The freezes are very difficult to replicate reliably. When they happen, > emacs is unresponsive and can only be killed from the outside. Any tips > on how to debug this would be greatly appreciated. See my previous post: http://thread.gmane.org/gmane.emacs.orgmode/86255/focus=86263 You can wrap `jit-lock--debug-fontify' with: (advice-add 'jit-lock--debug-fontify :around (lambda (fun &rest args) (with-local-quit (apply fun args)))) and then force emacs to break and display a backtrace by sending the SIGUSR2 to the emacs process. Best, -- Daimrod/Greg