technomancy/slamhound — Issue #12: Emacs 100% cpu use
Author: weissjeffm
Created: 2012-01-01 23:30:35+00:00
State: open

Env: Emacs24, swank-clojure 1.3.4, slamhound 1.2.0

If i run M-x slamhound on this:
--------
(ns blah)

(defn blahdy []
(split "sdf" #"s"))
-------

The first time, the result is what was already there. running a second time causes the emacs process to go to 100% CPU indefinitely. C-g aborts, freeing the CPU, and the result ends up being correct:
-------
(ns blah (:use [clojure.string :only [split]]))
-------

Maybe I didn't wait long enough, but I didn't think the emacs process is what should be doing the work - it should be swank, right? Given that the result is correct even when I abort, it seems like something at the very end of the elisp is hanging or spinning.