Adding a VS2022 issue to Troubleshooting

README.md

@@ -144,6 +144,7 @@ If Visual Studio cannot load the visualizer or you have other debugger visualize
 | The magnifier icon does not appear<img width="0px"/> | Debugger Visualizers are not installed for the Visual Studio version you use. Check the [installation steps](#installing-debugger-visualizers) above. Make sure you select the correct version from the list. |
 | Could not load this custom viewer.<br/>![Could not load this custom viewer.](https://kgysoft.net/images/DebuggerVisualizerTrShCouldNotLoadViewer.png) | Open _Debug / Options / Debugging / General_ and make sure that both _Use Managed Compatibility Mode_ and _Use legacy C# and VB expression evaluators_ are unchecked.<br/>![Debugging Options.](https://kgysoft.net/images/DebuggerVisualizerTrShCouldNotLoadSettings.png) |
 | An unhandled exception of type 'System.InvalidOperationException' was thrown by the custom visualizer component in the process being debugged. (Object is currently in use elsewhere.)<br/>![Object is currently in use elsewhere.](https://kgysoft.net/images/DebuggerVisualizerTrShObjectIsInUse.png) | You try to debug a `Graphics` instance, whose Device Context is in use (the `GetHdc` method has been called previously). This `Graphics` instance cannot be accessed until the `ReleaseHdc` method is called. |
+| The target process exited with code -2146233082 (0x80131506) while evaluating the function 'System.Runtime.CompilerServices.RuntimeHelpers.GetHashCode'.<br/>![The target process exited with code -2146233082 (0x80131506) while evaluating the function 'System.Runtime.CompilerServices.RuntimeHelpers.GetHashCode'.](https://user-images.githubusercontent.com/27336165/142195623-da48f880-84ab-43c5-949b-80faa800adc6.png) | Occurs in Visual Studio 2022 when attempting to debug a `Color` instance.<br/>The bug has been [reported](https://developercommunity.visualstudio.com/t/visual-sudio-2019-throws-a-nullreferenceexception-1/1142584#T-N1587256) to the VisualStudio team. |
 | Unable to perform function evaluation on the process being debugged (Unable to evaluate expression because the code is optimized or a native frame is on top of the call stack.)<br/>![Unable to evaluate expression because the code is optimized or a native frame is on top of the call stack.](https://kgysoft.net/images/DebuggerVisualizerTrShOptimized.png) | Can occur even with debug build, typically when debugging a .NET Core project. When it happens, then likely all members in the debug window show a similar error message. Perform a Step Over operation (F10 by default)/Set Next Statement (Ctrl+Shift+F10), or restart the debugging session and try again. |
 | Unable to perform function evaluation on the process being debugged (Function evaluation timed out)<br/>![Function evaluation timed out.](https://kgysoft.net/images/DebuggerVisualizerTrShTimeout.png) | It can happen that the visualizer loads too slowly for the first time. Just try to click the magnifier icon again, which usually solves the problem. If all members in the debug window show an error, then perform a Step Over operation first (F10 by default). |
 | Unable to load the custom visualizer (Operation is not valid due to the current state of the object)<br/>![Operation is not valid due to the current state of the object.](https://kgysoft.net/images/DebuggerVisualizerTrShOperationIsNotValid.png) | Typically happens after timeout. Likely all members in the debug window show a similar error message. Perform a Step Over operation (F10 by default)/Set Next Statement (Ctrl+Shift+F10), or restart the debugging session and try again. |