Very strange deadlock on Exception.ToString
I am troubleshooting a strange issue occurring in a game engine I'm writing. Normally, when an exception occurs in either the tick or render thread, a third "watchdog" thread will log the exception and then attempt to gracefully exit the entire process.
This works as expected on my desktop, but I recently tried to run the engine on my laptop (I was missing some assets so it threw an exception) and it is deadlocking instead of exiting gracefully. The deadlock is perplexing me, because it's occurring inside of very low-down .NET runtime code.
If I hit "Break" in Visual Studio while it is deadlocked, I can see that the watchdog thread is hung on the following line in my logging code:
If I break apart that code into concatenation, it hangs on
I'm half tempted to file an issue on the
This works as expected on my desktop, but I recently tried to run the engine on my laptop (I was missing some assets so it threw an exception) and it is deadlocking instead of exiting gracefully. The deadlock is perplexing me, because it's occurring inside of very low-down .NET runtime code.
If I hit "Break" in Visual Studio while it is deadlocked, I can see that the watchdog thread is hung on the following line in my logging code:
If I break apart that code into concatenation, it hangs on
exception.ToString()TypeNameParser.GetTypeSystem.Diagnostics.StackTraceSymbolsI'm half tempted to file an issue on the
dotnet/runtimeCall_Stack.txt6.76KB
