Memory leak when frequently updating line graph

[GoogleCodeExporter]

Running ELYCHARTS v2.1.5 on a Windows 7 OS

Starting with the line graph that is used as an example on the webpage, I made 
little modification except to have a fill underneath one of three lines.

I update the graph and call $("#chart").chart('clear'); and then issue the 
drawChart command every .5 seconds to have the webpage update with current 
values of the data. 

The lines each have 10 points.  Two of the lines maintain constant values for 
their data to show "thresholds."  I am really only concerned with updating the 
data for the third line.

When I run this program, it appears to have a bit of a problem hogging the 
processor and the values from the graph lag behind the values that are sent to 
the webpage, and it becomes very slow after about 11-12 minutes.  The page is 
very slow then and will eventually become entirely unresponsive.

Any thoughts on what I can do to release memory or somehow more gracefully 
produce a graph that changes as time passes?

Thank you.

Original issue reported on code.google.com by [email protected] on 15 May 2015 at 3:20

[GoogleCodeExporter]

Are you experiencing the same issue with every browser? 
(Firefox/Chrome/IE/Safari)

Can you create a jsbin/jsfiddle to reproduce the issue?

Have you tried to call chart without "clearing" every time?

Original comment by [email protected] on 16 May 2015 at 4:03

[GoogleCodeExporter]

I removed the reference to tooltips and it seems to be running faster.

When I tried to call chart without "clearing" every time, it went much,
much slower.

I do not know that tooltips solved my problem, but at least I am not having
the problem anymore.  If it happens again and I have more details, I will
update.

-- 
Molly Osterried | Trident Systems Incorporated
Senior Software Engineer, Integrated Systems Engineering Group
10201 Fairfax Boulevard | Suite 300 | Fairfax, VA 22030
voice:  703.267.2310 | fax: 703.273.6608
email: [email protected] | www.tridsys.com
 *Notice: The information contained in this email message is considered
confidential and proprietary to the sender and is intended solely for
review and use by the named recipient. Any unauthorized review, use or
distribution is strictly prohibited. If you have received this message in
error, please advise the sender by reply email and delete the message.*

Original comment by [email protected] on 26 May 2015 at 6:55