cygwin + java = unkillable java process, then BSOD (Blue Screen Of Death)

Crossing my fingers hoping that someone else has had and sol开发者_开发百科ved this problem..

I run cygwin on my office Windows XP Pro machine, and run maven on my java projects.

In about 1 out of every 30/40 mvn commands, the java command will hang with no output on the screen, and take up my entire CPU usage (I've got 2 CPUs). Nothing works to kill it, not ctrl-C, task manager, killpid, kill -9, nothing that I've tried. If I try to shutdown, windows hangs and I need to manually power down the machine. If I continue working then a while later another instance hangs so now I'll have both CPU's pegged, and a few seconds later, a Blue Screen of Death.

I've tried using javaw, no help.

Any other ideas?

Thanks folks.

Not an actual answer to your problem, but make sure you're running ProcessExplorer in the background.

First, this will reveal which process is the most hungry for CPU, if java or bash.exe.

Second, its kill command is much more reliable than a Ctrl-C. I've seen processes resist a Ctrl-C signal, but I have yet to see a process stand against a kill command from ProcessExplorer.