Skip to content

Set DOTNET_EnableDumpOnSigTerm when crash dumps are enabled#8980

Open
333fred wants to merge 1 commit intodotnet:mainfrom
333fred:collect-dumps-on-sigterm
Open

Set DOTNET_EnableDumpOnSigTerm when crash dumps are enabled#8980
333fred wants to merge 1 commit intodotnet:mainfrom
333fred:collect-dumps-on-sigterm

Conversation

@333fred
Copy link
Member

@333fred 333fred commented Feb 10, 2026

This will ensure that when the OS sends the language server a sigterm, we also get a dump of that.

This will ensure that when the OS sends the language server a sigterm, we also get a dump of that.
@333fred 333fred requested a review from a team as a code owner February 10, 2026 21:38
@333fred
Copy link
Member Author

333fred commented Feb 10, 2026

The main thing I'm concerned about here is whether this will be "too" verbose, creating dumps for otherwise ok scenarios. @dibarbet @JoeRobich for thoughts.

// Collect crashreport.json with additional thread and stack frame information.
env.DOTNET_EnableCrashReport = '1';
// Collect dumps when the process is sent a SigTerm as well
env.DOTNET_EnableDumpOnSigTerm = '1';
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Slightly worried we might get a ton of useless dumps - like for example if vscode is shutting down and kills the process. Can we check if that happens?

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

To some extent it might be reasonable in that the user has already set the crashdump path. But it would be pretty bad if they leave it on and fill up their machine with useless dumps that aren't real crashes.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can we have the user set this on an as needed basis using the new env args setting?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants