Too high bash CPU on dual-core 2 terms

[GoogleCodeExporter]

What steps will reproduce the problem?
1. open a mintty term with bash --login -i and duplicate it
2. observed on a dual-core machine, not on my single-core laptop
3.

What is the expected output? What do you see instead?

The two mintty bash process absorbed all available 
CPU, 50% each, busy waiting. There was no bash activity.

I couldn't even open a google chrome url, that's how I came to search 
for a problem at all.

What version of the product are you using? On what operating system?
beta3 xpsp2

Original issue reported on code.google.com by reini.urban on 13 Mar 2010 at 9:02

[GoogleCodeExporter]

Thanks for the report. Is the problem reproducible? And you're saying it was 
the 
mintty.exe processes that absorbed the CPU, not bash?

Are you using Cygwin 1.7.1 or a snapshot? If the latter, which one? (There's 
been quite 
a bit of work on locking during Cygwin process startup recently.)

Original comment by andy.koppe on 13 Mar 2010 at 9:57

[GoogleCodeExporter]

The two bash processes were busy, mintty not. But now I'm not surre anymore if 
it was 
beta2 or beta3

Latest official cygwin-1.7, no snapshot.
$ uname -a
CYGWIN_NT-5.1 ATGRZWN502840 1.7.1(0.218/5/3) 2009-12-07 11:48 i686 Cygwin

Unfortunately I'm rather busy.

It was reproducible, yes. But right now as I'm trying it is not repro anymore.

Original comment by reini.urban on 13 Mar 2010 at 10:30

[GoogleCodeExporter]

Hmm, I haven't managed to reproduce this on any of the machine I use, including 
a 
dualcore with XP. As it was the bashes that were hanging, this sounds more like 
some 
sort of mishap in the Cygwin DLL than something that mintty might have caused. 
Closing, 
with fingers crossed.

Original comment by andy.koppe on 17 Mar 2010 at 7:22

• Changed state: Closed