StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
text
Body
copied!<p>Your question is not very clear. You should try to provide as much debug/error log info as possible.</p> <h2>Hunch below</h2> <p>However, considering that you are using 100% of a CPU core, this sounds suspicious. Are you hogging threads? Are you using ThreadPool? .NET programs require at least a few spare ThreadPool threads to operate -- a couple of years ago, it used to be that if you hog up the threads in the ThreadPool (running never-ending loops etc.), and the number of free threads drop below 3, the system will crash. You should check the number of free threads in the ThreadPool if that's what you're using.</p> <p>This is only a hunch.</p> <h2>Summarizing the problem</h2> <p>However, I am trying to summarize your problem below. See if I get it right:</p> <ol> <li><strong>Program will hog 100% CPU time on <em>one</em> core only</strong> -- which suggests only one single thread (as more threads will be scheduled on another CPU) -- what kind of thing are you doing to that poor CPU core that will strain it like this???!!! Are you doing System.Threading.Thread.Sleep() occasionally to yield some CPU time back to the system? Have you marked your process as background priority instead of high?</li> <li><em><strong>n-1</em> program instances will run fine</strong> (n = number of cores).</li> <li><strong>The n-th program instance will fail</strong> (n = number of cores).</li> <li><strong>Failure is always with the inability to open up a window in the Windows UI.</strong></li> </ol> <h2>Failure pattern</h2> <p>This pattern seems to suggest that, when your last program hogs up 100% time on the <strong>last</strong> CPU, Windows processes are left fighting for CPU time.</p> <p>If you have one core free, then Windows processes can always run on that core and your UI will be responsive. Once you hog that up too, you may be seeing a time-out detected by Windows on unresponsive applications -- you may be straining the machine so much that Windows cannot function.</p> <p>To Test: Run <em>n</em> program instances (n = number of cores). Then run other programs. Will they be sluggish, or will they run fine?</p>

Querying!

Guidance

An individual column

Larger individual text columns get their own page to allow for proper reading.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload