Abstract: A diagnostic mechanism monitors execution of a user interface (UI) thread to detect execution of a long running task that may have caused the UI thread to become unresponsive. The execution time of the UI thread is monitored and when it exceeds a threshold, the UI thread's call stack is preserved to a mini-dump file. The completion time of the UI thread is also tracked and stored in a delay file. The mini-dump and delay files are then uploaded to a server where the collected data is aggregated overall execution runs by multiple users to identify the cause of the unresponsiveness.

Abstract: A diagnostic mechanism monitors execution of a user interface (UI) thread to detect execution of a long running task that may have caused the UI thread to become unresponsive. The execution time of the UI thread is monitored and when it exceeds a threshold, the UI thread's call stack is preserved to a mini-dump file. The completion time of the UI thread is also tracked and stored in a delay file. The mini-dump and delay files are then uploaded to a server where the collected data is aggregated overall execution runs by multiple users to identify the cause of the unresponsiveness.

Abstract: An immediate delay tracker tool listens for the occurrence of user-specified events that exceed a delay threshold. In an embodiment, the events are associated with immediate user actions processed by a user interface (UI) thread where the response time of the immediate user action requires an instantaneous response. When the event exceeds the delay threshold, the control flow of all the processes and/or threads in the system is recorded, filtered and then analyzed for the source of the delay.