Steevee28 wrote: > Digging deeper into the code reveals that "now" comes from Jive's > Framework::getTicks() which is a 32bit timer with 1ms resolution, thus > running at 1000Hz, thus it is prone to bugs related to its wrapping > after 49.7 days or even after 24.8 days if the value is dealt as a > signed value.
An interesting observation. It might a bit of a challenge to track down how "your issue" would come about from this. One possibility might be that a specific timer is set but never fires. As far as I am aware, the "number" type in lua is, by default, a "double float". Thus it would be possible for a timer to be set at a future time that never arrives. But that hypothesis would need checking in Squeezeplay's context, I believe that there may be tuning possibilities for the "number" type. One way of monitoring this might be to put in a trace into -jive.ui.Timer._insertTimer- and check if such a timer is ever set up. Perhaps a bit of a challenge if the effect of "missing" the timer is a reboot, because the log files will disappear. (-/var- is mounted on a ramfs). ------------------------------------------------------------------------ mrw's Profile: http://forums.slimdevices.com/member.php?userid=38299 View this thread: http://forums.slimdevices.com/showthread.php?t=111650 _______________________________________________ Radio mailing list [email protected] http://lists.slimdevices.com/mailman/listinfo/radio
