Abstract: Various embodiments discussed herein enable unique identifiers or hash values to be generated that uniquely identify performance issues and associated call stack units, which may be attributed to a user or team of users. A performance issue for a currently running process can be detected. A particular location within a call stack of the process indicating where the performance issue was detected can be determined. A quantity of call stack frames within the particular location that account for a threshold proportion of the performance issue can be determined. A hash value that uniquely identifies the performance issued can be generated based at least in part on the particular location and the quantity of call stack frames within the particular location that account for the threshold proportion of the performance issue.

Abstract: Various embodiments discussed herein enable intelligent resource leak detection and associated user interface. In some aspects, if a kernel sends a tracing event (e.g., an ETW event) after a process or application has been requested to be shut down but before the process has actually been shut down, a resource leak can be detected. This is because the application should have requested the reference indicator to be removed in memory before the tracing event, as opposed to the kernel acting alone without an application request to remove the reference indicator. If a reference indicator has not been requested to be removed by the time this tracing event occurs, then it is indicative of the application never having sent a request to remove the reference indicator, which is indicative of a resource leak.

Abstract: Various embodiments discussed herein enable intelligent resource leak detection and associated user interface. In some aspects, if a kernel sends a tracing event (e.g., an ETW event) after a process or application has been requested to be shut down but before the process has actually been shut down, a resource leak can be detected. This is because the application should have requested the reference indicator to be removed in memory before the tracing event, as opposed to the kernel acting alone without an application request to remove the reference indicator. If a reference indicator has not been requested to be removed by the time this tracing event occurs, then it is indicative of the application never having sent a request to remove the reference indicator, which is indicative of a resource leak.

Abstract: Various embodiments discussed herein enable unique identifiers or hash values to be generated that uniquely identify performance issues and associated call stack units, which may be attributed to a user or team of users. A performance issue for a currently running process can be detected. A particular location within a call stack of the process indicating where the performance issue was detected can be determined. A quantity of call stack frames within the particular location that account for a threshold proportion of the performance issue can be determined. A hash value that uniquely identifies the performance issued can be generated based at least in part on the particular location and the quantity of call stack frames within the particular location that account for the threshold proportion of the performance issue.