On Monday 2006-04-10 at 13:28:05 +0200, Mario S.Mommer wrote:
I've had no problems with slime _whatsoever_, and don't remember ever hitting a bug. The only things that have happened to me is that I discover by accident yet another feature :-)
I used to have trouble-free slime, too, but ever since December or so, on both Debian and Red Hat systems, I've been getting periodic "freeze ups" where I have to SIGTERM the lisp process and re-run M-x slime. It was only recently (when I read someone's comment -- here?) that I realised this occurs when CMUCL does its garbage collection. Turning GC off avoids the situation.
Does anyone know the solution to this?
Failing that, is there a quick and easy way to restart slime to get a fresh lisp image? (A sort of manual garbage collection! ;-))
I'm using recent CVS slime (various since December) and Emacs 21.4.1, with CMUCL 19a.
Thanks,
David