I just noticed that the Prototype script links to an internal version.  You can just
replace '/scripts/prototype.js' with 'https://ajax.googleapis.com/ajax/libs/prototype/1.7.0.0/prototype.js'.

Since there doesn't seem to be any indication that this will be fixed soon is there
source code available so that I can try to fix this myself?

We hope that this would be fixed soon, in the upcoming release.

I have noticed that this issue seems to be fixed.  I am just wondering if it is actually
fixed or if we need to keep our workaround in place?

Using the 15th of May 2013 release I still have this issue. 

Attached is a screenshot of the google chrome memory profile, and some google visualisation
code to demo the problem. It seems that some DOM elements and event listeners are never
released. 

Is the code open sourced? So I can look a this myself I could really do with this being
resolved quiet quickly. 

I am seeing the memory grow, but only while there is memory available, and not permanently.
 I don't see an always rising event listener count, for example, but it rises and falls.
 Memory rises and falls as well.  I am using Chrome 27.0.1453.93 on linux.

You can close issue 436, issue 209, issue 1313, issue 1225, issue 1073 and issue 1276
as duplicates of this issue.

To summarize, continuously calling theChartObject.draw(...) causes memory growth, with
just about any type of chart.
Continuously forcing a garbage collection (using the Timeline panel of the Google Chrome
Developer Tools) makes the memory grow a bit slower, but growth is exhibited nevertheless.

This happens in Google Chrome 30 and in Firefox. Note that in Firefox the memory does
not grow quickly, but it still grows.

An example of a page that has a real memory issue due to this problem is the Real Time
Google Analytics overview page -
https://www.google.com/analytics/web/?hl=en#realtime/rt-overview
Which seems to be using the Google Visualization API as well and redrawing its charts
every second or less.
In a little more than half an hour, the memory grows to over 640,000 KB (without forcing
a garbage collection), even when there is no new data.

Note that you must be logged in and have an active website profile, otherwise the page
is not available.

See issue chromium:306154, issue chromium:140028 and issue chromium:159038 for details.

Thanks for your report, and summary of prior duplicate and related issues.

We recently did a lot of work to clean up memory leaks and the next release should
resolve most if not all issues. (I haven't found any more leaks, but there always could
be more hiding in various corners I haven't found.) 

You should be able to see these fixes now if you load version 1.1 of google charts.

I tried it and saw a great improvement!

Google Analytics seems to be loading 1, not 1.1. Can you contact their team and help
them update to 1.1? The leak is very harsh in this specific case.

(I did it myself using the Developer Tools and there seemed to be a great improvement)

Or will "1" load this "1.1" version once it gets released?

Thank you for the prompt response!

Yes, "1", which always loads 1.0, will eventually load what is now 1.1 once it is released
so that replaces the 1.0 version. This rollover may happen in another week or so, assuming
we have stabilized things well enough.

Please do let us know if you find any more leaks.

Issue 1276 has been merged into this issue.

When is this "1.1" release happening?  Is there any way I can enable it on my site right
now?  I'm speaking in terms of the Google Analytics Real-time Overview page, which
is still suffering from this issue.

If the Google Analytics page with charts is not loading 1.1 now, they may have their
reasons for it.  (I missed that part of phistruck's question earlier.)  I try to make
sure they are aware of the situation.

The page for the bug in Chromium says this issue is fixed (https://code.google.com/p/chromium/issues/detail?id=140028)
 however, GA RealTime Analytics still leaks and crashes after the window is open for
more than 30 minutes. Depending on the system/browser/device the crash time differs.

You mentioned you would let them know, but the their bug is listed as closed referring
to this post,  you can see  kenjibaheux@chromium.org  comment at the bottom of the
bug page.

@pat.grady -
The issue is indeed closed, in both of these issue trackers, because the underlying
issues of the dependent products (if any) were fixed.
- Chromium currently has no issue (it apparently had an issue, but that was fixed a
while ago), because it reproduces in other browsers - it is a Google Analytics issue.
- Google Visualization fixed their issue in a subsequent release (1.1).
- Google Analytics has not updated the code to use the new, leak free (in this sense,
anyway) 1.1 API.

So, basically, if Google Analytics has an issue tracker, this issue should be open
there. I do not believe there is an official issue tracker, so you will just have to
nag them in a discussion or support group (if such group exists).

Other than that, the (underlying) issue is indeed fixed.