Abstract: A method is disclosed for performing message interactions in a multi-tab application program. The method includes creating one or more page windows corresponding to respective tabs in the multi-tab application program as one or more top-level windows and receiving an input message corresponding to a user operation with respect to a particular tab. The method also includes sending the input message to one of the page windows corresponding to the particular tab by a main frame window of the multi-tab application program in a non-blocking message sending mode, without sending any associated system message to the page windows. Further, the method includes continuing to handle messages for other page windows by the main frame window regardless whether the one of the page windows is hung.

Abstract: A method is disclosed for performing message interactions in a multi-tab application program. The method includes creating one or more page windows corresponding to respective tabs in the multi-tab application program as one or more top-level windows and receiving an input message corresponding to a user operation with respect to a particular tab. The method also includes sending the input message to one of the page windows corresponding to the particular tab by a main frame window of the multi-tab application program in a non-blocking message sending mode, without sending any associated system message to the page windows. Further, the method includes continuing to handle messages for other page windows by the main frame window regardless whether the one of the page windows is hung.

Abstract: A “Performance Evaluator” provides various techniques for tracking system events to diagnose root causes of application performance anomalies. In general, traces of system events involved in inter-thread interactions are collected at application runtime. These traces are then used to construct inter-thread dependency patterns termed “control patterns.” Control patterns are then evaluated to determine root causes of performance anomalies. Where an application terminates abnormally or full traces cannot be collected for some reason, partial control patterns are constructed for that application. In various embodiments, “fingerprints” are then generated from full or partial control patterns and are matched to fingerprints corresponding to operations in other control patterns extracted from reference traces collected on the same or similar systems. Matched fingerprints or control patterns are then used to deduce the root cause of application performance anomalies associated with full or partial traces.