Vince, I found one source of a memory leak: the webcam cronjob. In the webcam.debian file a number of variables were used like: WEBCAM_ID=4 CAMERA=picamera$WEBCAM_ID DATETIME=$(date +"%Y-%m-%d %H:%M:%S") EPOCH=$(date +"%s") ...
The memory which is used by these variables is not automatically freed after the cronjob task ends. You need to unset them like: unset WEBCAM_ID unset CAMERA unset DATETIME unset EPOCH ... Now the memory leak of the cronjob is minimal. Luc On Friday, 27 March 2020 23:34:22 UTC-3, Lucas Heijst wrote: > > Vince, > > These are the steps I will do: > 1. Stop mben, this will also stop cmon. Tfrc runs and the web photos are > taken starting at 06:00 tomorrow morning. > 2. When they are stable I will move cmon to tfrc. > 3. When tfrc, web photo and cmon are stable I will start the mben driver > but stop the mben service which handles the data of the mben driver. > > Luc > > On Friday, 27 March 2020 19:14:18 UTC-3, Vince Skahan wrote: >> >> On Friday, March 27, 2020 at 12:45:22 PM UTC-7, Lucas Heijst wrote: >>> >>> Vince, >>> >>> As I stated earlier, I have no knowledge how to get program modbusenergy >>> stable. >>> I only can monitor the difference in memory leak with different settings. >>> Restarting a program doesn't change the used memory. >>> >> >> Disable it. We need to see which of the many things you are running is >> the unstable thing. >> > -- You received this message because you are subscribed to the Google Groups "weewx-development" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/weewx-development/df470038-c175-4f49-ba90-a9356c408862%40googlegroups.com.
