Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

MSbuild crashes when run inside terminal #16489

Closed
gilknyaz opened this issue Dec 21, 2023 · 6 comments
Closed

MSbuild crashes when run inside terminal #16489

gilknyaz opened this issue Dec 21, 2023 · 6 comments
Assignees
@rainersigwald
Labels
Issue-Bug It either shouldn't be doing this or needs an investigation. Needs-Triage It's a new issue that the core contributor team needs to triage at the next triage meeting Resolution-External For issues that are outside this codebase

Comments

@gilknyaz
Copy link

gilknyaz commented Dec 21, 2023 •
edited
Loading

Windows Terminal version

1.18.3181

Windows build number

10.0.22621.0

Other Software

MSBuild (VS 2022)

Steps to reproduce

  1. Open the Developer Command Prompt for VS 2022 profile.
  2. go to a C# solution folder
  3. Run MSbuild to compile. (Or run msbuild /t:Restore to restore some nuget packages)

Expected Behavior

MSbuild to succeed

Actual Behavior

MSBuild starts working but stops very early. No error is written to the console.
In Event Viewer -> Application, the following error appears:

Faulting application name: MSBuild.exe, version: 17.8.3.51904, time stamp: 0xe31ab667
Faulting module name: combase.dll, version: 10.0.22621.2792, time stamp: 0xd9671289
Exception code: 0xc0000409
Fault offset: 0x00000000001522b2
Faulting process id: 0x0x6380
Faulting application start time: 0x0x1DA34154F6EE43B
Faulting application path: C:\Program Files\Microsoft Visual Studio\2022\Enterprise\MSBuild\Current\Bin\amd64\MSBuild.exe
Faulting module path: C:\WINDOWS\System32\combase.dll
Report Id: 4af61e29-3040-4862-b67c-0fb2c7a14aef
Faulting package full name: Microsoft.WindowsTerminal_1.18.3181.0_x64__8wekyb3d8bbwe
Faulting package-relative application ID: App
@gilknyaz gilknyaz added Issue-Bug It either shouldn't be doing this or needs an investigation. Needs-Triage It's a new issue that the core contributor team needs to triage at the next triage meeting labels Dec 21, 2023
@zadjii-msft
Copy link
Member

@rainersigwald any ideas? Or any idea how to investigate? Does this work just fine in the vintage console/?

@microsoft-github-policy-service microsoft-github-policy-service bot added the Needs-Author-Feedback The original author of the issue/PR needs to come back and respond to something label Jan 3, 2024
@rainersigwald
Copy link
Member

I haven't heard of this before. Since you have VS installed, you might be able to get more information by setting the environment variable MSBUILDDEBUGONSTART=1 before running MSBuild, which should pop up a JIT debugger prompt. Then the crash might have a bit more actionable information?

@gilknyaz
Copy link
Author

gilknyaz commented Jan 5, 2024 •
edited
Loading

@zadjii-msft @rainersigwald
MSBuild.001.zip
MSBuild.002.zip

I've uploaded the dump created with MSBUILDDEBUGONSTART
It's split because github doesn't allow more than 25MB per-file. Please rename them to MSBuild.zip.001 and MSBuild.zip.002 to open.

Another thing that might explain the difference - it happens to me on a Virtual Desktop machine. (VMWare VDI). Doesn't happen on a regular PC.

@microsoft-github-policy-service microsoft-github-policy-service bot added Needs-Attention The core contributors need to come back around and look at this ASAP. and removed Needs-Author-Feedback The original author of the issue/PR needs to come back and respond to something labels Jan 5, 2024
@zadjii-msft
Copy link
Member

@rainersigwald Hey can you investigate this more on your side? Or move this to the msbuild repo? I can't imagine that this is something that is really caused by Terminal code... but if this is something that explodes in msbuild cause we're running, I think you'd be best equipped to find out why

@zadjii-msft zadjii-msft removed the Needs-Attention The core contributors need to come back around and look at this ASAP. label Jan 10, 2024
@zadjii-msft zadjii-msft added the Resolution-External For issues that are outside this codebase label Jan 10, 2024
@rainersigwald rainersigwald mentioned this issue Feb 13, 2024
Open
@rainersigwald
Copy link
Member

This issue was moved to dotnet/sdk#38742

@rainersigwald
Copy link
Member

@zadjii-msft I copied this to dotnet/msbuild, feel free to close this one.

@carlos-zamora carlos-zamora closed this as not planned Won't fix, can't repro, duplicate, stale Jan 10, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@rainersigwald rainersigwald

Labels
Issue-Bug It either shouldn't be doing this or needs an investigation. Needs-Triage It's a new issue that the core contributor team needs to triage at the next triage meeting Resolution-External For issues that are outside this codebase
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@rainersigwald @carlos-zamora @zadjii-msft @gilknyaz