From mboxrd@z Thu Jan 1 00:00:00 1970 From: Fabrice Niessen Subject: Re: 24.4.1; Emacs hangs with Org mode when point is in LOGBOOK Date: Wed, 22 Oct 2014 10:12:12 +0200 Message-ID: <86lho81q1v.fsf@example.com> References: <8661fdegiz.fsf@example.com> <8761fdh0ai.fsf@ericabrahamsen.net> <87a94pfkua.fsf@gmail.com> Mime-Version: 1.0 Content-Type: text/plain Return-path: In-Reply-To: <87a94pfkua.fsf-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> (Thorsten Jolitz's message of "Tue, 21 Oct 2014 18:28:45 +0200") 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-mXXj517/zsQ@public.gmane.org Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org-mXXj517/zsQ@public.gmane.org To: Thorsten Jolitz Cc: emacs-orgmode-mXXj517/zsQ@public.gmane.org Thorsten Jolitz wrote: > Eric Abrahamsen writes: >> Fabrice Niessen writes: > >>> On Windows 8, with Emacs 24.4.1 (from Dani) and Org mode version >>> 8.3beta, I can very often freeze Emacs when clocking into a task, or >>> when editing the timestamps found in the LOGBOOK drawer. >> >> I've gotten something looking like that from time to time (more often >> in the early days of the Org caching mechanism), and sending SIGUSR2 >> to the frozen emacs would reveal that it was in the midst of >> something flyspell-related. I'm under Windows, though with Cygwin. Not sure if that procedure works... >> You don't appear to be running flyspell, I didn't tell about Flyspell, but though, yes, I'm using it everywhere, always. >> but I'll guess that Org's timers are clashing with somebody else's >> timers. Not very helpful, I know. > > I just crashed > > ,---- > | GNU Emacs 24.3.1 (x86_64-unknown-linux-gnu, GTK+ Version 3.12.2) > | of 2014-06-11 on var-lib-archbuild-staging-x86_64-jgc > `---- > > again today while refiling an Org task, but I already reported this a > few weeks ago to the Emacs maintainers and it seems I have a "stripped > binary" that does not deliver useful backtrace info. I don't use > flyspell and I'm on Archlinux. > > Not very helpful, I know. Yes, the problem is how to collect traces that can help people understand and fix the problem. Best regards, Fabrice -- Fabrice Niessen Leuven, Belgium http://www.pirilampo.org/