What would cause emacs to "mostly" freeze when creating an org agenda?

I say "mostly" because when you type C-g, it does show "Quit" in the minibuffer, and the time logging number in the minibuffer still increments. Nothing else seems to respond though that I could think of.

I was only able to get emacs to respond by getting the emacs pid with ps aux | grep emacs and then running kill -SIGUSR2 {PID}.

After that, emacs opened a buffer with:

Debugger entered--Lisp error: (quit)
  redisplay_internal\ \(C\ function\)()

What can I do to prevent this behavior?

  • 1
    Does this happen when you start emacs with emacs -q? – Tobias Apr 7 '16 at 5:18
  • It happens rarely, and is only reproducible within a session. If it happens once, it will likely happen again, but I can't get it to happen reliably. I haven't seen it happen with emacs -q, but I haven't tried running a -q session for days opening 100's of files (and even when I do that with a normal session I usually have no issues). – avv Apr 15 '16 at 17:52
  • Find an answer? Getting a similar issue – George Mauer May 22 '18 at 20:29

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Browse other questions tagged or ask your own question.