This page will explain how to use the Direct3D 11 Debug Layer to retrieve diagnostic information, warning and error messages coming from Firefox. The idea is that in some cases this may provide some insight as to why device resets are occurring.
== Installing Install required 3rd-party components ==
In order to use the Debug Layer Install the Windows SDK has to be installed on your machine, it can be found from [https://developer.microsoft.com/en-US/windows/downloads/windows-10-sdk here].
You also need an effective way of gathering the debug output on your systemsInstall DebugView, and will need to install a tool published as part of Microsoft SysInternals called DebugView; it can be found , from [https://technet.microsoft.com/en-us/sysinternals/debugview.aspx here].
== Toggle the Direct3D Debug Layer Pref in Firefox ==
Go to In about:config (in a recent nightly build), search for a set the boolean preference labeled 'gfx.direct3d11.enable-debug-layer'to true and restart Firefox. After you flip this, a restart is required, and Firefox will now begin outputting D3D11 diagnostic information to the Windows debug output layer.
== Gathering Gather Logging Info ==
The next step is to startup Start DebugView, go to 'File->Log As File', and log an unlimited size log to a file directory of your choice (this log file can grow somewhat large in size so you may want to keep that in mind). Now proceed to use Firefox as you normally would. After you experience a Device Reset, you can stop the logging in DebugView (by simply clicking File->Log As File again), and attach the log to a bug for evaluation by a Firefox graphics engineer.
Be aware that these Use Firefox as you normally would (if you can reproduce the problem at will, it may be worth running DebugView and Firefox as the sole applications on your system - see below for details.) After you experience a Device Reset, stop the logging in DebugView (by simply clicking File->Log As File again). == Submitting the collected information == The collected logs contain -debug output from all- of your running application's debug output applications, and as such may contain personally identifiable or privacy sensitive information if any of your applications are doing sloppy logging. With that in mind, you may want This is the reason to only run Firefox at + DebugView when planning on sharing the time that logs. Attach the logging is enabledlog to a [https://bugzilla.mozilla.org/enter_bug.cgi?product=Core&component=Graphics new] or existing https://bugzilla.mozilla.org bug for evaluation by a Firefox graphics engineer. You will also want to set the privacy checkbox when adding the attachment to bugzilla - the one that says "Make attachment and comment private (visible only to members of the core-security-release group)". This will ensure that any private information, if any, is not available to general public.
