From mboxrd@z Thu Jan 1 00:00:00 1970 From: York Zhao Subject: Re: still seeing semi-regular lockups Date: Sat, 28 Jun 2014 21:39:45 -0400 Message-ID: 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> <87ha3425s3.fsf@ericabrahamsen.net> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:42837) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1X145r-0001CH-Mq for emacs-orgmode@gnu.org; Sat, 28 Jun 2014 21:39:49 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1X145q-000772-MY for emacs-orgmode@gnu.org; Sat, 28 Jun 2014 21:39:47 -0400 Received: from mail-vc0-x235.google.com ([2607:f8b0:400c:c03::235]:42253) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1X145q-00076p-IE for emacs-orgmode@gnu.org; Sat, 28 Jun 2014 21:39:46 -0400 Received: by mail-vc0-f181.google.com with SMTP id il7so6194412vcb.26 for ; Sat, 28 Jun 2014 18:39:45 -0700 (PDT) In-Reply-To: <87ha3425s3.fsf@ericabrahamsen.net> 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 My experience of using `org-mode' (git commit "2824502" and previous versions) with Emacs 24.3.91 (git commit "0f0917d") had been a nightmare. I got bitten by this bug frequently, I was mad. Some of my `org-drill' entires might have been damaged to some extent. This was a problem with Emacs 24.3.1 ("3a1ce06") too but was much better, at least not damaging my `org-drill' flies. I will have to go back to Emacs 24.3.1. Appears to me that Emacs 24.4 may have some bad issues. On Sat, Jun 28, 2014 at 3:27 PM, Eric Abrahamsen wrote: > 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. > > After feeling like I was running behind the bus for a few weeks, I may > have finally gotten something useful. > > FWIW I *haven't* seen any log-drawer related lockups for a while now, > not since Nicolas said he fixed some things in that direction. But in > the past couple of days I have had a few flyspell-related lockups, and > finally got an uncompiled backtrace. > > This has happened the same way a few times now. A longish, text-heavy > file, with only three top-level headlines (one of them a footnote > section), and no drawers of any sort anywhere in the document -- very > little Org markup at all, actually. The lockup starts at random, and > SIGUSR2 shows me a very short backtrace related to a flyspell-mode > related advice somewhere (I didn't save this one, it's byte-compiled, if > it's important I'll clean out more compiled files and try to get it > again). > > I recover from that lock, turn off flyspell-mode in my org buffer, and > within three or four commands Org locks up again. This time the > backtrace is related to org cache, here's the one I just got, after > calling org-end-of-line: > > http://pastebin.com/Q0g8DmUa > > Hope that's useful! Let me know if I can provide anything else. > > E > >