If you write--version in the "Other flags" (motivation: I wanted to see the FSC version on each compile), and if you then switch to any source file, the whole of Visual Studio disappears.

Repro steps

Minimal repro zip file:CrashVisualStudio.zip

• Create a new solution + project in VS 2022
• Go to Project Properties and set "Other flags" to--version
• Switch back to the main source (i.e.,Ctrl+Tab or by clicking)
• Boom! The big disappearing act is complete:it crashes without any warning.

Second repro:

• Assume the abovefsproj change is saved
• Try to open the solution of project in VS 2022
• Bring focus to any source file in that project
• Boom! VS disappears again:it crashes without any warning.

See video capture (sorry for the delay, I hit Ctrl-S to save, as that is often another way of crashing):

Expected behavior

Not sure if--version is valid here, but valid or not, Visual Studio (version 2022) shouldnot disappear.

Actual behavior

Visual Studio crashes without a crash report. Sometimes there's an auto-restart which will hang, most of the times this restart does not happen. Sometimes child processes are killed, sometimes they remain around (likeMSBuild.exe).

Known workarounds

Don't use "additional compiler options" aka "other flags".

Related information

I only tested this on a Windows 10 machine, I could check a Windows 11 machine for good measure. Didn't test with VS Code, only VS 2022 Community Edition.