echarts-bot[bot] commented on issue #21383: URL: https://github.com/apache/echarts/issues/21383#issuecomment-3555588181
@SmartBigFeng It seems you are not using English, I've helped translate the content automatically. To make your issue understood by more people and get helped, we'd like to suggest using English next time. 🤗 <details><summary><b>TRANSLATED</b></summary><br> **TITLE** [Bug] Echart setOption updating data for a long time causes memory leaks **BODY** ### Version 5.6.0 ### Link to Minimal Reproduction https://jsfiddle.net/wangfengCode/fm6ucqxp/ ### Steps to Reproduce 1. Open the URL and download it locally and run chrome and edge in the browser 2. Open the console and switch to the memory tab 3. Click the record button every few minutes to check the snapshot memory size (you can click the garbage collection button interspersed) The memory has been growing In privacy mode, it runs for about 5 minutes <img width="1065" height="821" alt="Image" src="https://github.com/user-attachments/assets/74caf75a-7d3a-4e8c-900f-a00135c01fc5"; /> In normal mode, it runs for about 5 minutes in total <img width="863" height="808" alt="Image" src="https://github.com/user-attachments/assets/4fc7ae7b-3bc2-4eab-bc93-fa4ed8f00785"; /> ### Current Behavior Under the premise of drawing only one chart and using native JS unresponsive packaging, the memory in privacy mode increased by nearly 5M in five minutes, and the garbage collection button was clicked several times in the middle, while the real project required multiple charts, pushing data more and more frequently, and the online environment had the problem of memory overflow and finally crashing. ### Expected Behavior The current suspicion is that setOptions may have a potential memory leak, and I hope that officials will troubleshoot and fix the problem. ### Environment ```markdown - OS:Windows 11 - Browser:Chrome 142.0.7444.176 Edge142.0.3595.80 - Framework:Vue@3 ``` ### Any additional comments? #20151 has mentioned such issues and has been fixed, but there have been subsequent mentions that setOption may have a memory leak </details> -- 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: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
