Closed GoogleCodeExporter closed 9 years ago
Not sure if these observations would be helpful or not... I played a bit with
the number of images in the feed. And I noticed that with a small number of
images (4-5) and a long interval between them (30), the gadget would be able to
continue playing after the hiccup. But with a number of images in the feed
similar to what the customer wanted to display (20), the chrome memory would
shoot up from 7,000K to over 570,900K. And # handles for the chrome process
would go from 260 to 650 almost instantly. Then I would see 1-2 more chrome
processes, with memory consumption of 32,000K - 82,000K. And the presentation
would never recover... I also played with various feed formats -- atom, rss
0.91, 092, 1.00 and rss 2.0 with enclosures (all that Flickr offers), but the
gadget seems to play rss2 only.
Original comment by mark.kre...@risevision.com
on 27 Aug 2012 at 2:32
Original comment by donnapep@gmail.com
on 31 Aug 2012 at 8:05
http://067c5df50ab37cd38995-db651d7b6f74fb302777f4d25567e540.r56.cf2.rackcdn.com
/PhotoAlbum.xml
Original comment by donnapep@gmail.com
on 31 Aug 2012 at 8:06
Original comment by neal.god...@risevision.com
on 5 Sep 2012 at 1:18
Original comment by donnapep@gmail.com
on 11 Sep 2012 at 11:30
Original issue reported on code.google.com by
neal.god...@risevision.com
on 24 Aug 2012 at 9:20