100% CPU when starting emacs first time, without any progress of installation

[yingbo]

I tried emacs 25.3 on Mac and 25.1 on Linux, both have the same problem: After some "Opening TLS connection ..."... done" messages, emacs uses 100% cpu and just hang there. C-g can stopped it, but then there is nothing installed.

[rberger]

Same problem here on Mac 10.13.2, GNU Emacs 25.3.2.

Been running with 100% CPU for about 10 minutes. Not clear if I should force quit or let it run. But it doesn't seem happy.

[cowboyd]

@rberger what install of emacs are you using. Homebrew, emacsforosx, none of the above?

[rberger]

Its been a while. I can't really tell now. I thought it was some form of Homebrew (railwaycat/emacsmacport/emacs-mac). But I don't see it any form of emacs installed by hombrew. Is there a known good version to try? I'll try changing it.

Looks like its some form of Emacs mac port:

Copyright (C) 2009-2017  YAMAMOTO Mitsuharu

This file is part of GNU Emacs Mac port.

[cowboyd]

I've found that brew cask install emacs has been a reliable, if stodgy, implementation.

I used https://github.com/d12frosted/homebrew-emacs-plus for awhile and while it was more beautiful, it was definitely crashier.

[dylnclrk]

I ran in to this issue on a macbook running the latest high Sierra. I was installing emacs like this before:

$ brew install emacs --with-cocoa

I tried just randomly tacking on some more arguments,

$ brew install emacs --with-cocoa --with-ctags --with-imagemagick@6 --with-librsvg --with-modules

and it seemed to clear things up for me. Posting this just in case anyone wants to take a stab at narrowing my list down.

EDIT: I haven't tried the cask yet. But $ brew info emacs seems to encourage it:

==> Caveats
Please try the Cask for a better-supported Cocoa version:
  brew cask install emacs

So I would probably heed @cowboyd 's advice.

[yingbo]

I tried the emacs-plus which looks good too. The vanilla emacs from brew with default doesn't work. If it cannot be fixed, at least should be mentioned in readme or install that which settings are required.

[Robdel12]

I'm curious what is causing the CPU to peg. But yea, I agree, once we know more about it we should add it to the README.