From edbea6648d8a3a4100967cd2233164c3f390c73f Mon Sep 17 00:00:00 2001 From: Jason Malinowski Date: Thu, 11 Nov 2021 13:13:28 -0800 Subject: [PATCH] Don't capture dumps for out-of-sync generator drivers We understand the root cause now, so we won't need this. --- ...te.CompilationAndGeneratorDriverTranslationAction_Actions.cs | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/Workspaces/Core/Portable/Workspace/Solution/SolutionState.CompilationAndGeneratorDriverTranslationAction_Actions.cs b/src/Workspaces/Core/Portable/Workspace/Solution/SolutionState.CompilationAndGeneratorDriverTranslationAction_Actions.cs index 88ae4bc447234..df1b9727e7105 100644 --- a/src/Workspaces/Core/Portable/Workspace/Solution/SolutionState.CompilationAndGeneratorDriverTranslationAction_Actions.cs +++ b/src/Workspaces/Core/Portable/Workspace/Solution/SolutionState.CompilationAndGeneratorDriverTranslationAction_Actions.cs @@ -88,7 +88,7 @@ public TouchAdditionalDocumentAction(AdditionalDocumentState oldState, Additiona { return generatorDriver.ReplaceAdditionalText(oldText, newText); } - catch (ArgumentException ex) when (FatalError.ReportWithDumpAndCatch(ex)) + catch (ArgumentException ex) when (FatalError.ReportAndCatch(ex)) { // For some reason, our generator driver has gotten out of sync; by returning null here we force // ourselves to create a new driver in FinalizeCompilationAsync. This is the investigation for