Jan> "John A. Turner" <turner(a)blueskystudios.com&gt; writes: Jan> Oops, sorry. I meant I wanted Raymond to do that... Although Andy Jan> thinks it might a garbage collect thing, in that case setting Jan> always_gc should make it easier to reproduce. I've been doing that for the last several hours. I started xemacs -vanilla, did M-x load-lib RET, had gdb attach to the process and set always_gc to 1, and detached. Then I answered the prompt. It was using 100% CPU for a while, but now it uses 0% CPU unless it has focus. I can't leave my mouse there all day because I need to do real work too! :-) Actually it has something to do with fvwm screens. When I switch to a different screen xemacs stops using CPU. When I move the mouse back to xemacs, it starts using CPU again. As long as I stay in that screen, xemacs uses CPU. Weird. This also brings up something I've noticed but haven't narrowed done. Sometimes, especially with eudc, the focus is moved to someplace weird even though the mouse is over the xemacs window. Moving the mouse out and back in fixes this, but it's annoying. Slowly waiting for that always_gc crash.... Ray