From: Eric Abrahamsen <eric@ericabrahamsen.net>
To: emacs-orgmode@gnu.org
Subject: Re: still seeing semi-regular lockups
Date: Wed, 25 Jun 2014 01:22:01 -0700 [thread overview]
Message-ID: <87vbrph00m.fsf@ericabrahamsen.net> (raw)
In-Reply-To: 877g45jv61.fsf@tanger.home
Daimrod <daimrod@gmail.com> writes:
> Matt Lundin <mdl@imapmail.org> writes:
>
>> Eric Abrahamsen <eric@ericabrahamsen.net> writes:
>>
>>> Nicolas Goaziou <mail@nicolasgoaziou.fr> writes:
>>>
>>>> Hello,
>>>>
>>>> Eric Abrahamsen <eric@ericabrahamsen.net> 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.
>>
>> With the latest git, I've experienced three lock-ups/freezes this
>> evening when a) archiving a subtree to a file, b) changing a todo state
>> with repeating timestamp, and 3) calling C-c C-c in an org-capture
>> buffer. (I don't think this is due to a recent change - I've been
>> running into these lockups sporadically for several months.)
>>
>> The freezes are very difficult to replicate reliably. When they happen,
>> emacs is unresponsive and can only be killed from the outside. Any tips
>> on how to debug this would be greatly appreciated.
>
> See my previous post:
> http://thread.gmane.org/gmane.emacs.orgmode/86255/focus=86263
>
> You can wrap `jit-lock--debug-fontify' with:
>
> (advice-add 'jit-lock--debug-fontify :around
> (lambda (fun &rest args)
> (with-local-quit (apply fun args))))
>
> and then force emacs to break and display a backtrace by sending the
> SIGUSR2 to the emacs process.
I think the advice here was also to run Org uncompiled, as that produces
a more useful backtrace, is that right? A couple of times I've gotten
SIGUSR2 to knock emacs out of a lock, but it was only while I was
running a compiled org. The one time I was running uncompiled and got a
lock, even SIGUSR2 couldn't bring it back...
next prev parent reply other threads:[~2014-06-25 8:22 UTC|newest]
Thread overview: 70+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-14 8:39 still seeing semi-regular lockups Eric Abrahamsen
2014-05-15 9:21 ` Bastien
2014-05-15 9:30 ` Daimrod
2014-05-15 9:46 ` Bastien
2014-05-15 10:31 ` Eric Abrahamsen
2014-05-15 10:37 ` Daimrod
2014-05-15 10:43 ` Eric Abrahamsen
2014-05-19 14:21 ` Daimrod
2014-05-20 8:25 ` Eric Abrahamsen
2014-05-20 8:55 ` Daimrod
2014-05-20 11:16 ` Eric Abrahamsen
2014-06-24 8:48 ` Nicolas Goaziou
2014-06-24 14:28 ` Eric Abrahamsen
2014-06-25 4:09 ` Matt Lundin
2014-06-25 5:39 ` Matt Lundin
2014-06-25 7:32 ` Sebastien Vauban
2014-06-27 13:00 ` Nicolas Goaziou
2014-06-25 7:38 ` Daimrod
2014-06-25 8:22 ` Eric Abrahamsen [this message]
2014-06-25 8:30 ` Bastien
2014-06-25 8:40 ` Eric Abrahamsen
2014-06-25 13:47 ` Matt Lundin
2014-06-26 2:58 ` Matt Lundin
2014-06-26 3:00 ` Matt Lundin
2014-06-27 12:56 ` Nicolas Goaziou
2014-06-27 13:37 ` Alan Schmitt
2014-06-27 22:31 ` Nicolas Goaziou
2014-06-28 19:27 ` Eric Abrahamsen
2014-06-29 1:39 ` York Zhao
2014-06-29 2:23 ` Eric Abrahamsen
2014-06-30 1:15 ` York Zhao
2014-06-30 1:43 ` York Zhao
2014-06-30 20:20 ` Alan Schmitt
2014-07-01 0:43 ` York Zhao
2014-07-01 7:38 ` Nicolas Goaziou
2014-07-01 17:14 ` York Zhao
2014-07-01 21:15 ` York Zhao
2014-07-02 8:01 ` Nicolas Goaziou
2014-07-03 1:03 ` York Zhao
2014-07-06 7:28 ` Nicolas Goaziou
2014-07-06 14:40 ` York Zhao
2014-07-06 21:05 ` York Zhao
2014-07-06 21:31 ` Nicolas Goaziou
2014-07-07 0:16 ` York Zhao
2014-07-07 5:27 ` Nicolas Goaziou
2014-07-25 14:33 ` Sebastien Vauban
2014-07-07 1:43 ` York Zhao
2014-07-07 5:33 ` Nicolas Goaziou
2014-07-07 15:10 ` York Zhao
2014-07-03 15:31 ` York Zhao
2014-07-03 15:55 ` York Zhao
2014-07-06 7:19 ` Nicolas Goaziou
2014-07-06 14:29 ` York Zhao
2014-07-15 2:30 ` York Zhao
2014-07-19 3:17 ` Matt Lundin
2014-07-19 14:12 ` York Zhao
2014-06-29 13:58 ` Nicolas Goaziou
2014-05-29 3:01 ` Daimrod
2014-05-30 9:17 ` Nicolas Goaziou
2014-05-30 14:35 ` Daimrod
2014-06-11 11:53 ` Daimrod
2014-06-11 21:30 ` Nicolas Goaziou
2014-06-11 22:18 ` Daimrod
2014-06-14 7:43 ` Nicolas Goaziou
2014-06-14 23:55 ` Daimrod
2014-06-22 7:58 ` Nicolas Goaziou
2014-06-04 4:47 ` Eric Abrahamsen
2014-06-05 4:29 ` Daimrod
-- strict thread matches above, loose matches on Subject: below --
2014-05-14 11:06 dieter
2014-05-15 2:29 ` Eric Abrahamsen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87vbrph00m.fsf@ericabrahamsen.net \
--to=eric@ericabrahamsen.net \
--cc=emacs-orgmode@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).