From mboxrd@z Thu Jan  1 00:00:00 1970
From: Eric Abrahamsen <eric@ericabrahamsen.net>
Subject: Re: still seeing semi-regular lockups
Date: Tue, 20 May 2014 16:25:50 +0800
Message-ID: <87ppj86elt.fsf@ericabrahamsen.net>
References: <87siocrbyb.fsf@ericabrahamsen.net> <87siobtn1i.fsf@bzg.ath.cx>
	<87ha4r1j91.fsf@tanger.home> <87k39hdf2o.fsf@tanger.home>
Mime-Version: 1.0
Content-Type: text/plain
Return-path: <emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org>
Received: from eggs.gnu.org ([2001:4830:134:3::10]:34771)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <eric@ericabrahamsen.net>) id 1WmfJu-0006rN-CU
	for emacs-orgmode@gnu.org; Tue, 20 May 2014 04:22:53 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <eric@ericabrahamsen.net>) id 1WmfJk-0001jI-2V
	for emacs-orgmode@gnu.org; Tue, 20 May 2014 04:22:46 -0400
Received: from mail-yh0-f41.google.com ([209.85.213.41]:40959)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <eric@ericabrahamsen.net>) id 1WmfJj-0001j1-Ud
	for emacs-orgmode@gnu.org; Tue, 20 May 2014 04:22:35 -0400
Received: by mail-yh0-f41.google.com with SMTP id f73so88251yha.14
	for <emacs-orgmode@gnu.org>; Tue, 20 May 2014 01:22:35 -0700 (PDT)
List-Id: "General discussions about Org-mode." <emacs-orgmode.gnu.org>
List-Unsubscribe: <https://lists.gnu.org/mailman/options/emacs-orgmode>,
	<mailto:emacs-orgmode-request@gnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/archive/html/emacs-orgmode>
List-Post: <mailto:emacs-orgmode@gnu.org>
List-Help: <mailto:emacs-orgmode-request@gnu.org?subject=help>
List-Subscribe: <https://lists.gnu.org/mailman/listinfo/emacs-orgmode>,
	<mailto:emacs-orgmode-request@gnu.org?subject=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: Daimrod <daimrod@gmail.com>
Cc: Bastien <bzg@gnu.org>, emacs-orgmode@gnu.org


On 05/19/14 23:21 PM, Daimrod wrote:
> Daimrod <daimrod@gmail.com> 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...