search

apache / echarts

Apache ECharts is a powerful, interactive charting and data visualization library for browser
https://echarts.apache.org
Apache License 2.0
60.58k stars 19.62k forks source link

dynamic chart memory leak #10130

Open MyCupOfTeaOo opened 5 years ago

MyCupOfTeaOo commented 5 years ago

Version

4.2.0-rc.2

Reproduction link

https://mycupofteaoo.github.io/echartHtmlDemo/

Steps to reproduce

online Code is here

What is expected?

normal

What is actually happening?

Memory continues to rise This is a screenshot of about 30 minutes. image

echarts-bot[bot] commented 5 years ago

Hi! We've received your issue and please be patient to get responded. 🎉 The average response time is expected to be within one day for weekdays.

In the meanwhile, please make sure that you have posted enough image to demo your request. You may also check out the API and chart option to get the answer.

Have a nice day! 🍵

Ovilia commented 5 years ago

Please check if this has something to do with React. And provide a demo without React if not.

MyCupOfTeaOo commented 5 years ago

@Ovilia this is Pure HTML url Memory rose by 6 M in an hour image

Ovilia commented 5 years ago

@tz310200 Thanks!

ergouser commented 5 years ago

Is this a duplicate of/related to #7002?

ergouser commented 5 years ago

A quick search suggests #9437 and #8988 are possibly related issues.

ergouser commented 4 years ago

Is there an update or a milestone release for resolution of this issue (and the three related reports)?

This is not a "performance" issue, it's a critical issue that prevents production deployment of applications. Could we please mark it as such?

This issue is critical to all deployments of echarts. The only work-around is to periodically close out a browser completely, or reboot the whole computer system. It's most obvious in any application that dynamically refreshes charts and which is expected to run constantly, but ALL echarts applications are suffering because of these memory leaks. We committed to echarts expecting such a critical issue to be resolved fairly quickly, but #7002 was reported more than 2 years ago and there seems to be no progress.

pissang commented 4 years ago

Hi @ergouser Can you create a new issue and provide your reproducible demo to us? We can't reproduce the memory leak issue from the code in https://github.com/apache/incubator-echarts/issues/7002 and the link in this issue has been broken

MyCupOfTeaOo commented 4 years ago

您好@ergouser您可以创建一个新期刊并向我们提供可复制的演示吗？我们无法从＃7002中的代码重现内存泄漏问题，并且此问题中的链接已损坏 sorry,I modified the username after posting this issues I have updated the new link address

maneetgoyal commented 3 years ago

@MyCupOfTeaOo Are you running into this issue in ECharts 5.x as well?

h4de5 commented 3 years ago

we do see a similar issue running echarts 5.0.2 in angular

maneetgoyal commented 3 years ago

We also experimented a bit with a line chart whose data changed dynamically every few seconds or so. Recorded the heap for 60-70 minutes. Heap size grew a bit initially but later decreased down too, so memory leaks (if any) didn't seem to be very worrisome. The same test with Vega library weren't encouraging, however.

cc @SumitNegi7 @saikat-samanta

stereokai commented 2 years ago

Not only, but I can report that with line chart, even after refreshing the page, the old data doesn't get garbage collected. Calling instance.dispose() doesn't help either. I'm on v5.4

oldRabbitForz commented 2 years ago

Hi @ergouser Can you create a new issue and provide your reproducible demo to us? We can't reproduce the memory leak issue from the code in #7002 and the link in this issue has been broken 你不是在要demo,就是在要demo的路上

ergouser commented 2 years ago

The full html is in #7002. That issue was reported 5 years ago against 3.x so may, or may not still exist. I haven't tested against later versions.

0xAskar commented 1 year ago

Any updates on the memory leaks? After many hours, my code will crash and it will give the typical "Javascript memory heap out of memory" error