From 9df16555cfbb4bfd32c69f911e8fa1aa295028cb Mon Sep 17 00:00:00 2001 From: SAY-5 Date: Wed, 15 Apr 2026 10:08:52 -0700 Subject: [PATCH] Fix 'unhanded' / 'occured' typos in UnhandledExceptionDialog body text src/PerfView/Dialogs/UnhandledExceptionDialog.xaml.cs body text shown to the user when PerfView surfaces an unhandled exception had two typos: * 'An unhanded exception occured.\\r\\n' (line 19) * 'this exception went unhanded is a programmer error' (line 15) Both messages are presented in a WPF dialog to end users when an unhandled exception occurs. String-literal-only changes. --- src/PerfView/Dialogs/UnhandledExceptionDialog.xaml.cs | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/src/PerfView/Dialogs/UnhandledExceptionDialog.xaml.cs b/src/PerfView/Dialogs/UnhandledExceptionDialog.xaml.cs index 752ca17dc..66b9948bf 100644 --- a/src/PerfView/Dialogs/UnhandledExceptionDialog.xaml.cs +++ b/src/PerfView/Dialogs/UnhandledExceptionDialog.xaml.cs @@ -12,11 +12,11 @@ public UnhandledExceptionDialog(Window parentWindow, object exception) : base(pa { InitializeComponent(); - string reporting = "The fact that this exception went unhanded is a programmer error. It should be reported " + string reporting = "The fact that this exception went unhandled is a programmer error. It should be reported " + "so it can be fixed. Please set along the following stack trace information which will be " + "useful in diagnosing the problem.\r\n"; - Body.Text = "An unhanded exception occured.\r\n" + Body.Text = "An unhandled exception occurred.\r\n" + "\r\n" + "At this point you can opt to continue, however it is possible that the aborted computation will " + "cause additional failures. Because PerfView generally only opens files for reading, there is no "