From mboxrd@z Thu Jan 1 00:00:00 1970 From: Daimrod Subject: Re: still seeing semi-regular lockups Date: Tue, 20 May 2014 17:55:17 +0900 Message-ID: <874n0kde2y.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> Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:40733) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Wmfpg-0007m4-2k for emacs-orgmode@gnu.org; Tue, 20 May 2014 04:55:41 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1Wmfpa-0004FH-1t for emacs-orgmode@gnu.org; Tue, 20 May 2014 04:55:35 -0400 In-Reply-To: <87ppj86elt.fsf@ericabrahamsen.net> (Eric Abrahamsen's message of "Tue, 20 May 2014 16:25:50 +0800") 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: Eric Abrahamsen Cc: Bastien , emacs-orgmode@gnu.org Eric Abrahamsen writes: > On 05/19/14 23:21 PM, Daimrod wrote: >> Daimrod writes: >> >>> I have also semi-regular lockup with org-mode. I have opened a bug on >>> debbugs and here is what Stefan told me to try to debug this: >>> >>>> You can try `debug-on-event'. >>>> >>>> There's jit-lock-debug-mode but it doesn't disable inhibit-quit. >>>> So you'll need to additionally use >>>> >>>> (advice-add 'jit-lock--debug-fontify :around >>>> (lambda (fun &rest args) >>>> (with-local-quit (apply fun args)))) >>>> >>>> Of course sometimes this doesn't work because jit-lock-debug-mode >>>> changes the way things are executed and the bug may not manifest itself >>>> any more, but it's worth a try. >>>> >>>> Another source of info is to >>>> >>>> M-x trace-function RET org-adaptive-fill-function RET >>>> M-x trace-function RET org-element-at-point RET >>>> M-x trace-function RET org-element--cache-sync RET >>>> M-x trace-function RET org-element--cache-process-request RET >>>> >>>> Then reproduce the hang, then break the hang somehow (maybe with the >>>> jit-lock-debug hack above, or maybe with debug-on-event, or with C-g C-g >>>> C-g, ...), then look at the *trace..* buffer. >>> >>> I'll try to see what I can find this week end and report back. >> >> Ok, so the good news is the `debug-on-event' trick works. If you got a >> lockup, you can get a classic elisp backtrace by sending the SIGUSR2 to >> the Emacs process. >> >> The bad news is that I don't know yet how to reproduce the lockup. It >> seems to happen mostly (if not only) when I use org-mode + >> visual-line-mode + adaptive-wrap-prefix-mode + an input-method like >> latin-postfix. >> >> And it probably has to do with the cache mechanism. I'll try to >> reproduce it with the cache disabled but it hard to test because, as I >> said, I don't know how to reproduce it yet. >> >> I'll keep testing and see if I can reproduce it reliably. >> >> Stay tuned! > > Of course I haven't gotten a single lock-up since reporting in last time... :D Do you have a similar setup? That is visual-line-mode, adaptive-wrap-prefix-mode, input-method? -- Daimrod/Greg