From mboxrd@z Thu Jan 1 00:00:00 1970 From: Daimrod Subject: Re: still seeing semi-regular lockups Date: Mon, 19 May 2014 23:21:35 +0900 Message-ID: <87k39hdf2o.fsf@tanger.home> References: <87siocrbyb.fsf@ericabrahamsen.net> <87siobtn1i.fsf@bzg.ath.cx> <87ha4r1j91.fsf@tanger.home> Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:53214) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1WmOS2-0004I2-Oi for emacs-orgmode@gnu.org; Mon, 19 May 2014 10:22:11 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1WmORt-0003xB-MU for emacs-orgmode@gnu.org; Mon, 19 May 2014 10:22:02 -0400 In-Reply-To: <87ha4r1j91.fsf@tanger.home> (daimrod@gmail.com's message of "Thu, 15 May 2014 18:30:50 +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: Bastien Cc: Eric Abrahamsen , emacs-orgmode@gnu.org 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! -- Daimrod/Greg