fix: Remove AppDomain.CurrentDomain.ProcessExit hook on shutdown #4323
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Flash0ver
reviewed
Jul 7, 2025
Flash0ver
approved these changes
Jul 9, 2025
|
thx for the fix @jamescrosswell I'll verify once this gets to a released version (getsentry/sentry-powershell#85) |
|
Seems to work fine - no more hangs in CI getsentry/sentry-powershell#85 |
This was referenced Jul 28, 2025
This was referenced Aug 15, 2025
This was referenced Aug 18, 2025
This was referenced Aug 27, 2025
This was referenced Sep 8, 2025
This was referenced Sep 15, 2025
This was referenced Oct 2, 2025
This was referenced Oct 13, 2025
This was referenced Oct 20, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Resolves #3141
@vaind the repro involved adding the Sentry PowerShell package, which I assume wraps a specific version of the .NET SDK... so I wasn't sure how to go about testing whether this addressed the underlying error you were running into. Maybe building a new version of the powershell package or running a version of that package that is built using a source rather than package reference to sentry-dotnet?