I’m in the process of tracking down an issue* that, so far, I’ve only been able to confirm after running my applications for several days (seems like about 6 days is the trick, I’m trying to speed the failure up so I can debug faster).
This isn’t to point any fingers at Cinder, I’m assuming this issue is one I’ve introduced myself. (The Cinder library is great–even after weeks of running time, I see steady framerates, memory usage is flat and CPU usage is low… Thanks again to the maintainers and contributors!)
But I’m curious how long anyone out there has actually run their apps, without restart, in production. I once asked a partner/client to run an installation for a week, but later found out their technician would restart every AM anyway out of habit. (Despite ambitions, I’ve not yet had a chance to do a permanent or semi-permanent interactive.)
Also curious how many people choose to run at long intervals vs. people who intentionally trigger periodic restarts, and if anyone who has done long-running applications has run into any gotchas with any pieces of the Cinder lib.
*For the curious, on the chance that someone has a clue about the answer-- I have two separate animation systems to handle two different types of animations. One updates “by hand”, in that I update variables myself using time deltas calculated and passed on from Cinder’s update. That system is working fine. The other system uses tweens on Cinders main app::timeline()-- after a week, the animation value handled by that system begin to stutter. Again, app seems to be fine otherwise-- framerate is steady, and the other animation system remains smooth.