Abstract: Thread blocking synchronization event analysis software uses kernel context switch data and thread unblocking data to form a visualization of thread synchronization behavior. The visualization provides interactive access to source code responsible for thread blocking, identifies blocking threads and blocked threads, summarizes execution delays due to synchronization and lists corresponding APIs and objects, correlates thread synchronization events with application program phases, and otherwise provides information associated with thread synchronization. The visualization may operate within an integrated development environment.

Abstract: A thread execution analyzer analyzes blocking events of threads in a program using execution data and callstacks collected at the blocking events. The thread execution analyzer attempts to identify an application programming interface (API) responsible for each blocking event and provides blocking analysis information to a user. The blocking analysis information may be used by a developer of the program to understand the causes of blocking events that occur for threads of the program.

Abstract: A thread execution analyzer analyzes blocking events of threads in a program using execution data and callstacks collected at the blocking events. The thread execution analyzer attempts to identify an application programming interface (API) responsible for each blocking event and provides blocking analysis information to a user. The blocking analysis information may be used by a developer of the program to understand the causes of blocking events that occur for threads of the program.

Abstract: Thread blocking synchronization event analysis software uses kernel context switch data and thread unblocking data to form a visualization of thread synchronization behavior. The visualization provides interactive access to source code responsible for thread blocking, identifies blocking threads and blocked threads, summarizes execution delays due to synchronization and lists corresponding APIs and objects, correlates thread synchronization events with application program phases, and otherwise provides information associated with thread synchronization. The visualization may operate within an integrated development environment.

Abstract: Techniques are provided for performing font subsetting. One or more font subsetting parameters are received. The one or more font subsetting parameters indicate a granularity level for which font subsetting is performed for portions of a data container. The font subsetting parameters indicate a font subsetting granularity level other than an entire document associated with the data container. A first portion of the data container is determined in accordance with the font subsetting granularity level. A subset of font data for at least one font family is determined in accordance with what font data for the at least one font family is actually used by the first portion. The subset of font data is embedded in an output for a consumer.

Abstract: XPS documents are created and accessed via a collection of interfaces of various classes of an application programming interface. The application programming interface includes a document sequence class for reading and writing the document sequence of the XPS document, a fixed document class for reading and writing the fixed documents of the document sequence, a page class for reading and writing the pages of the fixed documents, and a resource class for accessing the resources of each page. Applications seeking to create or read XPS documents may utilize the application programming interface such that the complexities of creating and accessing the XPS document are abstracted away.