helgasoft commented on issue #19984:
URL: https://github.com/apache/echarts/issues/19984#issuecomment-2138811121
correct observation, can confirm.
```
cnt = 0;
setInterval(function () { ...
if (cnt++ % 20 ==0) console.log(performance.memory.usedJSHeapSize);
});
```
A progress table of _usedJSHeapSize_ change after 180 (20*9) updates.
showSymbol: true | showSymbol: false
------------ | -----------
130121792 | 42828236
144218209 | 47866032
151430246 | 47950212
156291700 | 49143991
160956740 | 50432808
174964166 | 46047918
180142251 | 47375168
188515739 | 48728521
**201940791** | 44206139
However _jsHeapSizeLimit_ is 2,172,649,472 and GC moves in mysterious ways,
so I'm not sure if this is a real problem...
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: commits-unsubscr...@echarts.apache.org
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscr...@echarts.apache.org
For additional commands, e-mail: commits-h...@echarts.apache.org
