From mboxrd@z Thu Jan 1 00:00:00 1970 From: Matt Lundin Subject: Re: still seeing semi-regular lockups Date: Wed, 25 Jun 2014 08:47:16 -0500 Message-ID: <87egyd14pn.fsf@fastmail.fm> 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> <877g45jv61.fsf@tanger.home> Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:41253) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1WznXo-0006ox-3p for emacs-orgmode@gnu.org; Wed, 25 Jun 2014 09:47:30 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1WznXi-0007sp-5F for emacs-orgmode@gnu.org; Wed, 25 Jun 2014 09:47:24 -0400 Received: from out1-smtp.messagingengine.com ([66.111.4.25]:59426) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1WznXh-0007si-Uy for emacs-orgmode@gnu.org; Wed, 25 Jun 2014 09:47:18 -0400 In-Reply-To: <877g45jv61.fsf@tanger.home> (daimrod@gmail.com's message of "Wed, 25 Jun 2014 16:38:30 +0900") 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: Daimrod Cc: emacs-orgmode@gnu.org Daimrod writes: > Matt Lundin writes: > >> >> 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. > Thanks, that's helpful. It seems jit-lock--debug-fontify is the development emacs. I'll build that in a moment... For the record, I've been seeing these lockups with stable releases of emacs (currently 24.3). Thanks, Matt