Background:
We're running into severe Chromecast performance issues when cycling through
different features on a page such as Google Maps, YouTube, and Calendar within
the first 10 to 15 minutes. To try to workaround the performance problem we
tried reloading the page after sometime, like 5 minutes after the page was last
loaded in order to clean up any cache, scripts, and processing on the
Chromecast device. However, while something like window.location.reload(true)
reloads the page, the performance of the Chromecast doesn't change.
What steps will reproduce the problem?
- Cast a page that causes Chromecast to slowdown and have it auto reload before the performance degrades
- Or use a very simple webpage we're created at http://www.scarlatt.com/performance_test_reload.html to reproduce the issue. Simply Cast this page on Chromecast using an app. This page basically cycles through YouTube (using embedded iframe) and Google maps (also inside an iframe) every 30 seconds and will refresh itself at around 3 minutes using window.location.reload(true);
What is the expected output? What do you see instead?
Expected behavior: Reloading the page should help improve the page's
performance by in essence cleaning it up when it's reloaded.
Actual behavior: Even though the page is reloaded every few minutes the
Chromecast still gets very slow in about 10 minutes (hangs) as if the reload
doesn't help boost the performance.
What version of the product are you using? On what operating system?
We’ve verified this issue on both Chromecast V1 and V2.
The firmware for Chromecast V2 is 1.16.44433
The firmware for Chromecast V1 is 1.17.46278
Please provide any additional information below.
Since profiling doesn’t work well on Chromecast we haven’t been able to get
it’s performance results. However we’ve profiled on the Chrome browser and
everything seems stable and runs not stop.
Attached the test html file pointed to by the url above.
Original issue reported on code.google.com by hir...@gmail.com on 24 Nov 2015 at 9:37
Original issue reported on code.google.com by
hir...@gmail.com
on 24 Nov 2015 at 9:37Attachments: