Bugzilla – Bug 5518
reports of clock screensaver lockups
Last modified: 2008-12-15 11:56:36 UTC
there are several reports of the clock screensaver locking up after extended use: http://forums.slimdevices.com/showthread.php?t=38466 at this point it would probably be best to further characterize the issue to see what's causing the failure, and if the lockup is truly related to the clock or if that's just what's on the screen at the time of the lockup.
Ross and myself have been discovering this over the last few days. The analogue and block screensavers die with an OOM error, the digital one works ok (over 1.5 days before system crash). Dunno the cause yet, should be easy to track as running on the jive remote they crash in around an hour.
From r501: It looks like the clock screensavers don't create a memory leak, but the lua garbage collector was not finishing a full gc cycle before the application crashed when these apps are running on the device. Longer term we might need to think how the ui objects (surfaces, tiles, etc) can be measured by the lua gc. At the moment these objects are only freed when lua does a full collection, but don't weight into the equation when working out when the collection is needed. For a short term workaround this check slighly improves the amount of memory used by the screen savers, especially the analogue clock (which was redrawing every second). I suspect these will still crash with OOM errors eventually.
Please just let me know what other testing is needed.
This should be fixed now. Ross can you please test all the clocks. Thanks.
Tested each screen saver for more than 24 hours and there were no failures.
Last comment should read each CLOCK not screen saver.
This bug has been fixed in the latest release of SqueezeCenter! Please download the new version from http://www.slimdevices.com/su_downloads.html if you haven't already. If you are still experiencing this problem, feel free to reopen the bug with your new comments and we'll have another look.