Add directions for getting crash dumps from Task Manager. (#4990)

* Add directions for getting crash dumps from Task Manager.

diagnostics/README.md

@@ -2,9 +2,10 @@
 This folder contains directions for gathering various detailed diagnostics/logs when reporting WV2-related issues. There's generally no need to proactively get any of these diagnostics before opening an issue, but if one seems obvious feel free to get it before opening an issue. Otherwise, a WV2 developer might link you to one of these pages to help them investigate an issue:
 
 - [Crash Dumps](crash.md): Crash dumps are used to better understand why a WV2 process is crashing and firing a [ProcessFailed](https://learn.microsoft.com/dotnet/api/microsoft.web.webview2.core.corewebview2.processfailed) event.
+- [Crash Dumps from Task Manager](task_manager_dump.md): There are cases where crash dumps aren't automatically generated and need to be collected manually.
 - [ETW Trace](etw.md): Event Tracing for Windows (ETW) traces include detailed events on system state and the activities WV2 was doing before and when an issue occurs.
 - [Installer Logs](install.md): Installer logs include information about any errors that WV2's installer/updater hit when trying to install or update the WV2 runtime.
 - [GPU Info](gpu.md): GPU logs include details on the user's GPU and any potential graphics or rendering issues.
 - [Network Logs](network.md): Network logs include the network requests, responses, and details on any errors when loading files.
 - [Code Integrity](code_integrity.md): how to root cause STATUS_INVALID_IMAGE_HASH errors.
-- [Test in Canary](test_canary.md): how to test new WebView2 runtime changes by using Edge Canary.
+- [Test in Canary](test_canary.md): how to test new WebView2 runtime changes by using Edge Canary.

diagnostics/task_manager_dump.md

@@ -0,0 +1,15 @@
+# Crash Dump from Task Manager
+Normally, crash dumps are gathered automatically and available in the app's user data folder (see [Crash Dumps](crash.md)). In some cases, a user might need to manually gather a crash dump, normally for unresponsive processes. To do so:
+
+1. Open Task Manager (Ctrl+Shift+Esc).
+2. Click "Details" on the left menu.
+3. Sort by the "Name" column.
+4. Scroll to find "msedgewebview2.exe"
+5. To find the right msedgewebview2.exe, you can use a combination of:
+    1. The "Package name" column, which will represent the application using WebView2. (you might need to right-click the column headers, choose "select columns" and check the box for "Package name")
+    2. The "Description" column, which will describe which of WebView2's processes it is. (you might need to make Task Manager very wide to see this one, you can drag to re-arrange the columns if needed)
+
+    For example, if you're asked to get a crash dump of "Outlook's Manager process", you'll want the process that has "Outlook" as its Package name, and "WebView2 Manager" for its Description.
+6. Right-click the process on the list and choose "Create memory dump file"
+7. Once that completes, click "Open file location"
+8. Copy the msedgewebview2.DMP file to a location where you can share it.