ddl puller(ticdc): Fix memory retention issue in ddlPullerImpl's PopFrontDDL method #11794
+1
−0
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.
What problem does this PR solve?
Issue Number: close #11793
What is changed and how it works?
Problem
In the
PopFrontDDL
method ofddlPullerImpl
, the operationh.pendingDDLJobs = h.pendingDDLJobs[1:]
creates a new slice by slicing the existing one. However, this leaves the first element (pendingDDLJobs[0]
) still referenced in the underlying array, potentially causing memory retention issues.If the removed element (a
Job
object) occupies significant memory and is no longer needed, this could lead to increased memory usage since it cannot be garbage collected.Solution
The fix ensures that the reference to the removed element is explicitly set to
nil
before updating the slice. This helps the garbage collector to reclaim memory associated with the removed element.Code Changes
h.pendingDDLJobs[0] = nil
before updating the slice inPopFrontDDL
.Updated code snippet:
Check List
Tests
Questions
Will it cause performance regression or break compatibility?
No.
Do you need to update user documentation, design documentation or monitoring documentation?
No.
Release note