Fix memory leak issue in policy evaluation #2872
Merged
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.
Description
In
org.dependencytrack.policy.AbstractPolicyEvaluator
, there is aQueryManager
created while instance initialization,dependency-track/src/main/java/org/dependencytrack/policy/AbstractPolicyEvaluator.java
Lines 37 to 41 in a7e5122
and later overwrite by it's setter which is called in
VulnerabilityAnalysisTask
execution, therefor the older instance ofQueryManager
will never get closed, so it leads to a memory leak.dependency-track/src/main/java/org/dependencytrack/policy/PolicyEngine.java
Line 88 in a7e5122
Addressed Issue
#2785 (comment)
Additional Details
Checklist