5

My Emacs 24.5.1 is not responding frequently recently on my MacBook Pro Yosemite 10.10.3. I have installed it from emacs for mac osx. Emacs window does not open, it shows Not Responding in the Activity Monitor. Sometimes it launches successfully without all these symptoms.

What can be the reason for this? Is the latest version of the Emacs is buggy for mac or there is a different known reason for that?

Improve this question
14
  • I see similar problems when the system is starting up. Waiting until initial background processes have completed before launching emacs helps, but it is hard to diagnose exactly. – Andrew Swann Jun 9 '15 at 13:28
  • in my case it is not after the system start up necessarily. – sçuçu Jun 9 '15 at 13:29
  • occasionally I have temporal "not responding" issues when opening files or show the content of a subtree in org-mode, I can't figure out why. I am using Emacs 25.0, plan to upgrade it to the newest version to see if I can get rid of the problem. – yi.tang.uni Jun 9 '15 at 14:04
  • is emacs doing something at startup that is trying to show you a dialog box? I (and many others it seems) have issues with emacs freezing completely when it tries to present a dialog box. – casey Jun 9 '15 at 21:11
  • 1
    Are you by any chance one of those people who never ever reboot their computer and just put it in sleep mode (by closing the lid) and expect it to work perfectly day after day, month after month, year after year? :) What other programs do you have running that might be causing some sort of a conflict? Have you gone through the startup and removed programs that load automatically to try and reduce the possibility of conflicts -- System Preferences/Accounts/Login Items? Are you running Emacs in daemon mode? Any other details you can provide regarding your setup that might give us a clue? – lawlist Jun 10 '15 at 7:37
3

This is a known problem in the current release of Emacs. It is fixed in the upcoming release of Emacs 25.

The underlying cause is that input events started to arrive before the initialization code was done.

The problems were more prominent when the system was low on resources or when under heavy load, e.g. when Emacs was launched at system startup.

Improve this answer

Your Answer

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

Not the answer you're looking for? Browse other questions tagged or ask your own question.