> Please upgrade to 1.5.9 and/or the latest snapshot to see if either help.
Thanks for the response; unfortunately upgrading did not help. I still don't know what triggers the behaviour, and it may be over an hour of use before the problem occurs, but when the CPU hits 100%, xemacs and each instance of bash are involved. Is it simplistic of me to wonder if there's a regression to the bug to which this URL refers? http://www.cygwin.com/ml/cygwin/2000-04/msg00522.html Or perhaps there are many plausible ways in which the symptoms I've described can occur(?) Thanks again, Graham ---------------------------------------------------------------------- > >Hi, > > > >I believe this is an old problem, but I'm now experiencing it with a > >recent version of Cygwin. I haven't been able to determine what > >triggers this, but after what seems like a few minutes working with > >bash, I find that my CPU is at 100%, and that task manager identifies > >the culprits as csrss.exe and each instance of bash.exe. Killing each > >copy of bash restores the CPU to its typical workload. I'm using > >version 1.5.7 of the cygwnin DLL, and Windows XP Pro > >SP1. Unfortunately I can't pinpoint when this started, and so identify > >what changed on the machine. I did set "tty" in the CYGWIN variable, > >but have since removed that setting. > > > >I've searched the mailing lists, but only found a tantalising > >suggestion that this would be fixed back in 1.1.1: > > > >http://www.cygwin.com/ml/cygwin/2000-04/msg00522.html > > > >Google found a couple of articles, but no fix. Does anyone know what > >is the cause of this? > > > >I've attached the suggested cygcheck output to this message. -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
