On Sat 05 Jul Remy Lavabre wrote: > The only solution I've found to avoid this problem is to set up a cron job > that closes WeeWX once a week and restarts it automatically. The memory is > freed up automatically.
Python's long had problems with memory leaks one way or another. Long ago I set up a daily cron job that stops weewx, takes a backup of the database, and re-starts it. It's seldom down for more than a few minutes, and the memory gets cleaned up at least daily... Another Pi-based system I'm using does a lot of very intensive imaging work in a Python framework during the hours of darkness. It goes a step further, and re-boots the Pi every day at a slack time of day to avoid memory-leak-related problems. Of course that Pi is dedicated solely to that task, so there are no other users to be caught out by sudden re-boots. -- 73, Rick, M0LEP -- You received this message because you are subscribed to the Google Groups "weewx-user" group. To unsubscribe from this group and stop receiving emails from it, send an email to weewx-user+unsubscr...@googlegroups.com. To view this discussion visit https://groups.google.com/d/msgid/weewx-user/1f0cb.686916e4.2b768%40hewett.org.
