does win8/8.1/10 kill/end-task long-running programs automatically as stated in specs? how specifically does it detect a locked-up process?

has this been put into windows 7 at any time to make it similar to windows 8?

Please supply accurate answers. thank you.

My understanding the reason for this change was to handle locked-up programs.

I do have a number of long-running processes. some examples of mine and scenarios for other users:

• simulations on a Workstation or HPC Server
• doing a directory tree walk on a hard disk with >=1TB of data

reference articles I have found on the subject:

windows 7

http://windows.microsoft.com/en-us/windows/exit-program-not-responding#1TC=windows-7

windows 8

From some of what I understand, you can also get the "Program Not Responding" or similarly titled dialog box when:

• bug in the source code of the program in question. for instance, while(1){} such as forever loops (win7)
• similar program bug when declaring a function one way but defining it a different way and then calling it (mismatch in function signature) (win7)
• similar to above with DLLs in using MSVCRT*.DLL or other
• (?) can't remember for sure on this, but I think some badly formed calls or it was invalid values or data type mismatch to Win32 API can do this from buggy code. (win7)
• for (x=0; x < 16777216; x++) {your code here...} in other words, large values for loop termination (win7)

this is a repost of http://answers.microsoft.com/en-us/windows/forum/windows_8-performance/does-win88110-kill-long-running-programs/d35c3c9e-c6f4-4bbf-846a-2041bf2167a0?tm=1427518759476

here due to a request to do so.

• Edited by Jim Michaels 5 hours 6 minutes ago