On Tue, Apr 01 2014, Robert Marshall <[email protected]> wrote: > On Tue, Apr 01 2014, Uday Reddy <[email protected]> wrote: > >> Robert Marshall writes: >> >>> When there's a long delay waiting for the messages to arrive emacs is >>> thrashing the CPU so it's not a network problem - or at least not one >>> where it's timing out on something. >> If there are run-away processes that shouldn't be there, you should either >> kill the Emacs session and restart, or you can use your elisp knowledge to >> `delete-process' all the offending subprocesses. I don't know a better way. >> > > It is looking likely that this is a problem with the latest emacs build > rather than vm - I'm now trying running on a non-latest build and *so far* I > can't see the problem. I'll give it to the end of the day and if the bug > doesn't reappear (so then it would appear to be changes in the emacs src > trunk) I'll then need to try to get some test case together that I can > get an emacs bug report together and I'll try profiling it when the bug > is active. >
Just to report back (if you don't read g.e.help) that it was a problem with that build of emacs - I was running out of pure space and I had to rebuild with a larger value of SYSTEM_PURESIZE_EXTRA Robert -- La grenouille songe..dans son château d'eau Links and things http://rmstar.blogspot.com/
