Skip to content
Switch branches/tags
Go to file

Latest commit

It seems We can't safely emulate D3D11_RESOURCE_MISC_SHARED_KEYEDMUTEX
with D3D11_RESOURCE_MISC_SHARED without introducing race conditions with
applications which use IDXGIKeyedMutex to synchronize multiple contexts
in a single process (e.g, IE11.)

But we can't blindly honour IDXGIKeyedMutex either without introducing
deadlocks with applications which use IDXGIKeyedMutex to synchronize
contexts across multiple processes (e.g, WarThunder.)

So compromise here by always trying to honour IDXGIKeyedMutex methods,
but never deadlocking.

Git stats


Failed to load latest commit information.
Latest commit message
Commit time

About apitrace

apitrace consists of a set of tools to:

  • trace OpenGL, Direct3D, and DirectDraw APIs calls to a file;

  • replay OpenGL and Direct3D calls from a file;

  • inspect OpenGL and Direct3D state at any call while retracing;

  • visualize and edit trace files.

See the apitrace homepage for more details.


TL;DR: Apitrace is still being maintained, but the maintainer has very little time to work on it, so patches/issues/requests are addressed if/as time permits.

Long version here

Obtaining apitrace

To obtain apitrace either download the latest binaries for your platform if available, or follow these instructions to build and install it yourself.

On 64bits Linux and Windows platforms you'll need apitrace binaries that match the architecture (32bits or 64bits) of the application being traced.


Detailed usage instructions are available here.