perf(lines): fix potential memory leak in the effect line when setOption with notMerge #16525
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.
Brief Information
This pull request is in the type of:
What does this PR do?
Reproduce demo of memory leak demo: https://uzedc5.csb.app/map-random.html
When we using setOption with notMerge. The model will be recreated but view will be reused. And the graphic elements in the view are also reused so we can apply transition animations easily.
In this case memory leaks happens in
echarts/src/chart/helper/EffectLine.ts
Line 162 in e4bdd30
lineData
:I still can't figure out why this
lineData
will be kept in the closure because there is no code using it in the during callback. Current workaroud is move the code of updating animation to a new function.Another improvement is removing the unnecessary hold of
SeriesModel
instance in the graphic elements inecharts/src/chart/helper/Symbol.ts
Line 46 in e4bdd30
Details
Before: What was the problem?
The instances of
SeriesData
andSeriesModel
in memory will increase each timesetOption
in the above case.After: How is it fixed in this PR?
The instance numbers of
SeriesData
andSeriesModel
is stable.