View source for QA/Platform/Graphics/Topcrashes in Drivers

The purpose of this project is to identify the most concerning crashes occurring in graphics drivers and escalate those issues to developers. These crashes do not fit the typical definition of a ''topcrash'' but could potentially be one of the top reasons users abandon Firefox.

* [https://crash-stats.mozilla.org/search/?product=Firefox&_facets=adapter_driver_version&_facets=adapter_device_id&_facets=signature&_columns=date&_columns=signature&_columns=product&_columns=version&_columns=build_id&_columns=platform#facet-adapter_driver_version All crashes with device/driver facets]
* [https://docs.google.com/spreadsheets/d/1NaaOUuQqcBW-NIGcOWoS45xt4UGerupbBnip2mzAkVU/edit#gid=1152683011 Tracking spreadsheet]

; Process
* ''Once per week'' update the crash volume and use that to determine triage priority (triage highest volume first)
* Click the link for the driver you want to investigate
* Select the ''Signature Facet'' tab and click the top signature which does not have an associated bug report
* Click the ''See equivalent Report list page'' link at the top of the report
* Make note of any high correlations such as operating systems, product versions, and graphics adapter chipsets/families from the ''Signature Summary'' tab
* Click one of the reports from the ''Reports'' tab
* Click the ''Report this bug in Core'' link to report a bug
* Include the following information in the report:
** A copy of the stack from the report
** A link to more reports with the same signature
** Correlations to a particular operating system, driver, chipset, and graphics card
** Any comments with relevant information which might be worth following up
** Any URLs you find in the reports which might be worth testing
* Be sure to add ''topcrash-nvidia'', ''topcrash-amd'', or ''topcrash-intel'' to the QA Whiteboard field
* ''See {{bug|1181349}} as an example''