Abstract: A Resource Dependency Viewer for graphics processing unit (GPU) execution information is disclosed. The Resource Dependency Viewer provides profiling/debugging information concurrently with information about execution flow, resource utilization, execution statistics, and orphaned resources, among other things. A user-interactive graph (“dependency graph”) may be provided via a graphical user interface to allow interactive analysis of code executed on a GPU (e.g., graphics or compute code). Resource utilization and execution flow of encoders may be identified by analyzing contents of a GPU workload representative of a GPU execution trace to generate the dependency graph. Information about dependencies and execution statistics may be further analyzed using heuristics to identify potential problem areas. The dependency graph may include visual indicators of these problem areas.

Abstract: A Resource Dependency Viewer for graphics processing unit (GPU) execution information is disclosed. The Resource Dependency Viewer provides profiling/debugging information concurrently with information about execution flow, resource utilization, execution statistics, and orphaned resources, among other things. A user-interactive graph (“dependency graph”) may be provided via a graphical user interface to allow interactive analysis of code executed on a GPU (e.g., graphics or compute code). Resource utilization and execution flow of encoders may be identified by analyzing contents of a GPU workload representative of a GPU execution trace to generate the dependency graph. Information about dependencies and execution statistics may be further analyzed using heuristics to identify potential problem areas. The dependency graph may include visual indicators of these problem areas.

Abstract: Systems, methods, and computer readable media to visualize execution history with a shader debugger are described. Various implementations present a first graphical user interface (GUI) for navigating through an executed graphics frame and receive with the first GUI at least one user input that defines a region of interest. In response to receiving the user input, the shader debugger presents a second GUI that includes execution history of a first graphics processor thread associated with the region of interest. After receiving a second user input with the second GUI to switch to a second graphics processor thread associated with the region of interest, the shader debugger updates the second GUI with the execution history of the second graphics processor thread.