|
1 | 1 | # Gathering Diagnostics and Logs |
2 | | -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: |
3 | 2 |
|
4 | | -- [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. |
5 | | -- [Memory Dumps from Task Manager](task_manager_dump.md): Sometimes a user might need to manually gather a memory dump, normally for unresponsive processes. |
6 | | -- [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. |
7 | | -- [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. |
8 | | -- [GPU Info](gpu.md): GPU logs include details on the user's GPU and any potential graphics or rendering issues. |
9 | | -- [Network Logs](network.md): Network logs include the network requests, responses, and details on any errors when loading files. |
10 | | -- [Code Integrity](code_integrity.md): how to root cause STATUS_INVALID_IMAGE_HASH errors. |
11 | | -- [Test in Canary](test_canary.md): how to test new WebView2 runtime changes by using Edge Canary. |
| 3 | +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. |
| 4 | + |
| 5 | +| Logs | Description | |
| 6 | +|-----------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| |
| 7 | +| [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. | |
| 8 | +| [Memory Dumps from Task Manager](task_manager_dump.md) | Sometimes a user might need to manually gather a memory dump, normally for unresponsive processes. | |
| 9 | +| [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. | |
| 10 | +| [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. | |
| 11 | +| [GPU Info](gpu.md) | GPU logs include details on the user's GPU and any potential graphics or rendering issues. | |
| 12 | +| [Network Logs](network.md) | Network logs include the network requests, responses, and details on any errors when loading files. | |
| 13 | +| [Code Integrity](code_integrity.md) | How to root cause STATUS_INVALID_IMAGE_HASH errors. | |
| 14 | +| [Test in Canary](test_canary.md) | How to test new WebView2 runtime changes by using Edge Canary. | |
| 15 | +| [Procmon](procmon.md) | Can be helpful for cases where we get file not found error or access denied. | |
| 16 | +| [Time Travel Debugging](ttd.md) | Instructions for using Time Travel Debugging. | |
| 17 | + |
0 commit comments