How long does windows wait before deciding a window is unresponsive and brings up the the unresponsive chrome? Just from anecodotal experience, I assume it is different in XP and Vista, as they are handled very differently by the DWM in Vista and the Explorer shell in XP.
-
It is based more on the number of outstanding items in the message queue than a time interval.
-
I vaguely remember reading about a 5 second wait after the application has stopped fetching messages from the message queue before windows labels the app as unresponsive. I will try to post a link if I ever find that article again :)
-
Taken from Windows Error Reporting at MSDN
An application is considered unresponsive (or hung) if it does not respond to Windows messages for five seconds and the user is trying to interact with the application.
SDX2000 : +1 Good job Zuu :)
0 comments:
Post a Comment