Memory Leak with Chrome

185 views
Skip to first unread message

colind...@gmail.com

unread,
Mar 21, 2013, 12:14:17 PM3/21/13
to google-visua...@googlegroups.com
Hi guys

I have been using the API to display real time data with 8 different type of charts in one webpage. Data is pushed out to the client and the datatable updated. The charts are redrawn every one second.

With Firefox, my example runs fine over a 24 hr period, but with Chrome the examples crash. Looking at the Chrome task manager, there is a huge increase in memory over a short period. If the redraw interval is increased (redraw every 10 seconds), this will slow the increase in memory down. So I think the problem is with draw function with the charts.

Even with the basic example running at https://developers.google.com/chart/interactive/docs/gallery/gauge there is a considerable increase in memory over time with Chrome. The three gauges on this page that update at different intervals.

Have people noticed problems like this with Visualization and Chrome previously?? Large increases in memory use while updating charts in Chrome?

Thanks

asgallant

unread,
Mar 21, 2013, 12:20:37 PM3/21/13
to google-visua...@googlegroups.com
Yes, this is a known issue (search the forum for "memory leak" for the reports).

colind...@gmail.com

unread,
Mar 22, 2013, 2:51:16 AM3/22/13
to google-visua...@googlegroups.com
Is there any solution to this issue coming down the tracks?
Message has been deleted

colind...@gmail.com

unread,
Mar 25, 2013, 7:40:35 AM3/25/13
to google-visua...@googlegroups.com
Hi

I tested out my a simplified version of my example (moving window line chart only) in the Chrome Canary build on Friday. I left the example running over the weekend in Canary and the results were positive. From this test run, it appears that the Canary build doesn't suffer as much from a memory leak compared to Chrome V25.  

Has anybody else experienced this???

Thomas Rybka

unread,
Mar 25, 2013, 10:14:47 AM3/25/13
to google-visua...@googlegroups.com
I'm on Chrome 27 (dev) and couldn't repro the case with the Gauge chart (the example page).

FWIW, I ran just the frame with the gauges, not the whole page, to make sure I isolated any other widgets from devsite or +1 buttons or whatnot.

Thomas Rybka | Software Engineer | try...@google.com | GViz


--
You received this message because you are subscribed to the Google Groups "Google Visualization API" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-visualizati...@googlegroups.com.
To post to this group, send email to google-visua...@googlegroups.com.
Visit this group at http://groups.google.com/group/google-visualization-api?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.
 
 

Yuhao Feng

unread,
May 9, 2017, 1:03:30 PM5/9/17
to Google Visualization API, colind...@gmail.com
Hi anyone had any fix on this? I'm doing the exact same thing, memory leak is killing it..
Reply all
Reply to author
Forward
0 new messages