Flush logs when crashing.

When the process is running, we use a finally block to call Log.Dispose and flush any outstanding logs to disk before the process exits. This works when we handle any exception in a matching catch block.

When the exception is unhandled, then the finally block will not run and instead the process will just exit. To fix this, flush the logs inside a catch block instead before rethrowing the error. This ensures we get logs even when crashing.
This commit is contained in:
RoosterDragon
2024-08-03 11:18:46 +01:00
committed by Gustas
parent 8a56e14d7a
commit 323204014c
4 changed files with 39 additions and 9 deletions

View File

@@ -80,6 +80,7 @@ namespace OpenRA.WindowsLauncher
}
finally
{
// Flushing logs in finally block is okay here, as the catch block handles the exception.
Log.Dispose();
}
}