If you have a Presentation with several instances of the Spreadsheet Gadget, all updating once a second, the memory climbs gradually so that it cannot run the Presentation for 24 straight hours.

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Play the Presentation below on a Display with at least 4 gigs of RAM.
2. Notice that the Presentation does not run for 24 hours, instead if starts 
giving low memory errors after about 12 - 18 hours and crashes the Presentation.

What is the expected output? What do you see instead?
The Display should run for 24 hours and restart as expected, without any low 
memory errors, especially if the machine has a strong enough CPU/Memory amount.

Please provide any additional information below.
Here is a link to the Presentation you can use: 
http://rdn-test.appspot.com/#PRESENTATION_MANAGE/id=8166ed82-cf4d-430a-b909-4871
5b472450/company=f9b6c2e9-d850-4a1f-b685-cea62a6563b4

Original issue reported on code.google.com by robb.pr...@risevision.com on 10 Sep 2012 at 1:42

[GoogleCodeExporter]

It should be mentioned that depending on the strength and memory capacity of 
the machine, the time before you get the memory message and the Presentation 
crashes can be different.

Original comment by robb.pr...@risevision.com on 10 Sep 2012 at 1:43

[GoogleCodeExporter]

Original comment by robb.pr...@risevision.com on 10 Sep 2012 at 6:37

• Added labels: Priority-High
• Removed labels: Priority-Medium

[GoogleCodeExporter]

A one second refresh rate is far too frequent. When I ran the Presentation, I 
received 503 errors from Google indicating that they had detected unusual 
traffic from my network, and asked that I enter a Captcha code so that they 
know I'm not a robot. The refresh rate needs to be increased to a reasonable 
amount for each instance of the Gadget. If there is still an issue at that 
point, we can address then.

Original comment by donnapep@gmail.com on 10 Sep 2012 at 9:14

[GoogleCodeExporter]

We discovered that when using DDE, if you lower the refresh rate to 2 seconds 
instead of 1 second, the Presentation becomes more manageable, however the 
memory still climbs. It appears it will run for 24 hours without crashing, but 
it si still climbing and not letting up, indicating a memory leak.

Original comment by robb.pr...@risevision.com on 12 Sep 2012 at 8:57

[GoogleCodeExporter]

Original comment by donnapep@gmail.com on 14 Sep 2012 at 2:16

• Changed state: Started

[GoogleCodeExporter]

The memory leak exists inside of the Google Visualization API. I am unable to 
fix the leak because it is against Google's terms of service to download and 
host the code.

The only alternative I think we have at this point is to try using the Google 
Spreadsheets API instead. I don't know too much about it, so I'm not entirely 
sure if it would even meet our needs. We'd have to determine that first before 
deciding whether or not we want to overhaul the Gadget.

Original comment by donnapep@gmail.com on 14 Sep 2012 at 6:53

[GoogleCodeExporter]

You really need a data source that updates frequently like Alex K. has access 
to in order to confirm this issue.

Test URL - 
http://6bfb3abceed8012d4f29-3bc983760bd76b1f0d9a644a2b859aaf.r19.cf2.rackcdn.com
/GoogleSpreadsheet.xml

Temporary URL equivalent to the above to use for Rise Display clients. This URL 
will be removed once testing has passed - 
https://s3.amazonaws.com/Gadget-Spreadsheet-Temp/GoogleSpreadsheet.xml

Original comment by donnapep@gmail.com on 21 Sep 2012 at 6:50

• Changed state: Fixed

[GoogleCodeExporter]

Original comment by robb.pr...@risevision.com on 4 Oct 2012 at 8:22

• Changed state: Verified

[GoogleCodeExporter]

Original comment by donnapep@gmail.com on 5 Oct 2012 at 8:29

• Changed state: Deployed