From mboxrd@z Thu Jan 1 00:00:00 1970 From: Daimrod Subject: Re: still seeing semi-regular lockups Date: Thu, 15 May 2014 19:37:00 +0900 Message-ID: <878uq31g6r.fsf@tanger.home> References: <87siocrbyb.fsf@ericabrahamsen.net> <87siobtn1i.fsf@bzg.ath.cx> <87ha4r1j91.fsf@tanger.home> <87bnuzl4em.fsf@ericabrahamsen.net> Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:38766) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Wkt2D-0004hE-SP for emacs-orgmode@gnu.org; Thu, 15 May 2014 06:37:10 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1Wkt2A-0002dW-Im for emacs-orgmode@gnu.org; Thu, 15 May 2014 06:37:09 -0400 Received: from mail-pa0-x22e.google.com ([2607:f8b0:400e:c03::22e]:61977) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Wkt2A-0002dK-B4 for emacs-orgmode@gnu.org; Thu, 15 May 2014 06:37:06 -0400 Received: by mail-pa0-f46.google.com with SMTP id kq14so918383pab.33 for ; Thu, 15 May 2014 03:37:05 -0700 (PDT) In-Reply-To: <87bnuzl4em.fsf@ericabrahamsen.net> (Eric Abrahamsen's message of "Thu, 15 May 2014 18:31:13 +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: emacs-orgmode@gnu.org Eric Abrahamsen writes: > Daimrod writes: > >> Bastien writes: >> >>> Hi Eric, >>> >>> Eric Abrahamsen writes: >>> >>>> After Nicolas made the last round of improvements to the caching >>>> mechanism I got far fewer hangs with Org, but they are still happening. >>>> Maybe once a day or so, on average, editing something in an Org buffer >>>> causes emacs to hang, and my fans to spin up, and there we are until I >>>> kill emacs. > > [...] > >> 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. >> >> By the way, if you want to see in which part the infloop occurs, you can >> attach a gdb debugger to the running emacs, source the >> /src/.gdbinit file and use the `xbacktrace' command. >> >> $ gdb >> gdb) source /src/.gdbinit >> ... >> gdb) xbacktrace >> >> You can also use the `bt' command but it contains much more noise. > > Thanks! This is the sort of thing I assumed I'd have to do, and it's > good to have an actual recipe. If you're on it, I might take the lazy > option and spectate for now... :) No problem, but could you attach gdb during a lockup, source .gdbitinit and use the `xbacktrace' command to see if the lockup happens at the same place? -- Daimrod/Greg