Re^3: control-C to "jumpstart" windows process (frees)

My testing shows "$x++ while 1" continues to consume 100% of the CPU even when I have text in the console window selected. Trying to write output to a frozen window will certainly freeze the program (as your test showed, I assume, based on the fact that you report being able to see the counter increment).

- tye

Comment on Re^3: control-C to "jumpstart" windows process (frees)

Replies are listed 'Best First'.
Re^4: control-C to "jumpstart" windows process (frees) by jimt (Chaplain) on Oct 18, 2006 at 16:30 UTC
That's a good point - I had my little test program constantly printing out, and that did indeeded freeze. I tweaked it to only print out every 10 passes through the loop, and sure enough that counter did continue to increment properly until it hit the next print, then it froze. So that does imply that it it continues to work and only locks up on output. Quick edit mode was enabled, which I just shut off. I'll keep my fingers crossed that this was indeed the solution.	[reply]

Replies are listed 'Best First'.

Re^4: control-C to "jumpstart" windows process (frees)
by jimt (Chaplain) on Oct 18, 2006 at 16:30 UTC

That's a good point - I had my little test program constantly printing out, and that did indeeded freeze. I tweaked it to only print out every 10 passes through the loop, and sure enough that counter did continue to increment properly until it hit the next print, then it froze. So that does imply that it it continues to work and only locks up on output.

Quick edit mode was enabled, which I just shut off. I'll keep my fingers crossed that this was indeed the solution.

[reply]