Fix DiagnosticListener memory leak #16047
Merged
Conversation
This file contains 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
This was referenced Jun 12, 2019
Closed
ajcvickers
approved these changes
Jun 12, 2019
DescriptionApplications that call Customer ImpactReported through support, and will likely also impact other customers, including those running on Azure. Regression?Yes. This leak did not exist in 2.1. ( RiskVery low; avoid creating the instance when it is not needed. |
|
Approved for 2.2.6. Checkin the fix now. |
|
@roji Don't check in! The branch is not ready yet--I'm working on it.. |
ghost
deleted the
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.
When IsConfigured is called, it applies all services. This caused a DiagnosticListener to get instantiated on each DbContext instantiation, and since it wasn't disposed it caused a leak.
Fixes #15173
PR for master (3.0): #16046
(cherry picked from commit 904ad9c)