I haven't seen the JSFiddle page error out after about 90 minutes of letting it run, so it's possible that my problem involves some other interaction that I removed for code simplicity. The only two other pieces that interact with the widget are the sockets from Socket.IO and the graphs being embedded in a draggable/sortable widget that gets dynamically inserted into the DOM at initial page load.
While I haven't seen the page crash, I have seen the memory usage balloon in the Chrome Task Manager. The original tab is up to 818 MB after 90 minutes and the second tab I opened is up to 215 MB after about 5 minutes. I have yet to see that number drop down as you observed, so there may be a platform inconsistency here. I'll test on my home Fedora installation when I leave work today to see if it's machine/OS dependent. > -- You received this message because you are subscribed to the Google Groups "Google Visualization API" group. To view this discussion on the web visit https://groups.google.com/d/msg/google-visualization-api/-/t24Hzj-1mpkJ. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/google-visualization-api?hl=en.
