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:
@@ -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();
|
||||
}
|
||||
}
|
||||
|
||||
Reference in New Issue
Block a user