Domoticz

With:
Version: 2024.4 (build 15910)
Build Hash: 0f2fcff99
Compile Date: 2024-02-10 12:56:24
dzVents Version: 3.1.8

I still experience memory leaks. First used the release 2024.4 version, now using the latest beta. No difference.

Current workaround is restarting every night with a cronjob.

Some info: In total Domoticz is connected to approx 800 devices, and a mix of 24 blockly, lua and dzvents scripts.

Before reverting to an old version I appreciate thoughts and comments.

You cannot revert back to an older version, at least I would not advise it. If so you have to go back to an old database too.
You are showing memory usage of the machine. Is memory usage of the Domoticz process showing the same issue (see motherboard sensor device Process Usage)? If not it is another process on your machine that requires memory.
It seems you are not using Python plugins so it should be in the scripts somewhere.

You are using a 2024.beta, did it happen with the previous beta too?

For the same database version you could go back to 15 January 2024, database version changed that day to 167.

Thanks your thoughs and comments.

I did not use a previous beta. Previously I used the release versions. It started last with the update in december. But in the meantime I also created additional scripts such as a (gas) degreesdays script.

Good point about the system mem. However I am certain it is the domoticz process, since restarting solves the issue. For example. This is the current system mem This is the domoticz mem usage: After: sudo service domoticz.sh restart
Is there a way to quickly determine the memory usage of the Domoticz subprocesses?

Many thanks again for your support.

Perhaps someone knows a better way to debug this but I would start with disabling the degreeday script for a day and see if the memory leak stays.

Do you restart only the Domoticz process or the complete system? You have a device called "process usage", please check that to be sure it is Domoticz (probably is)

You could try to look for the culprit with programs like gdb and pmap, but that is a tedious process.
I had the same kind of issue at the end of december / start of januari.
I my case I found out that it had probably to do with a system update in mid of december, I did not investigate which program was the 'bad guy'
But it might have to do with 'python3-urllib3'
I have a btrfs system and make snaphots every hour/day, so I just put the system back to before that update, and my problem was solved.

I only restart domoticz with: sudo service domoticz.sh restart. I am 100% sure it is domoticz process

@Kedi, I am afraid that I have to rebuild the system from scratch and step by step add configuration.

I have seen situations that scripts running external commands that are not correctly closed create memory resource issues.

So check the scripts that run external commands.

Yes I will start with that part.

Hello i am running domoticz 2024.4 and i have the same problem... did you find where it comes from ?
(running domoticz on windows 11)

I did some testing last weeks. The leak correlates with enabled hardware, not with any script. More enabled hardware = more memory leaking away.

Herewith a image. Yesterday evening I disabled most of the hardware. At 3:30 the daily restart occurs. At 9:00 I disabled all hardware, except the PI-sensors. 11:30 I started to enabled hardware again.

Since I have in total about 800 devices I need to restart demoticz daily as after a day of two the OOM-killers kills the Domoticz process.

Today I installed the latest beta. Same issue persists.

Is it really that my instance is the only one that has memory leaks? If I start with a brand new install the same issue occurs. Cannot believe that I'm the only one having this issue.

No you are not the only one. I also have a small memory increase every day until I get an unresponsive Domoticz after a few weeks.
Still have not figured out what the cause is, but keep looking.

This is my setup:
Raspberry Pi reference 2023-05-03
Raspbian GNU/Linux 11 (bullseye)
Linux pi 5.10.103-v7l+ #1529 SMP Tue Mar 8 12:24:00 GMT 2022 armv7l GNU/Linux
Raspberry Pi 4 Model B Rev 1.5
Domoticz: Version: 2024.4 (build 15910)
Build Hash: 0f2fcff99
Compile Date: 2024-02-10 12:56:24
dzVents Version: 3.1.8
Python Version: 3.9.2 (default, Mar 12 2021, 04:06:34) [GCC 10.2.1 20210110]

Maybe comparing setups with memory-leaks and without leaks helps finding the root-cause.

Anybody else (not) having the same issue?

I am experiencing the simular behaviour. Running 2024.3 on a RPI Zero (made the build myself). I am now thinking of letting monit restart domoticz when it passes 75Mb of memory ( if total memory > 75.0 MB for 5 cycles then restart ). System info:

Version: 2024.3
Build Hash: 3503953dd
Compile Date: 2024-01-24 08:40:07
dzVents Version: 3.1.8
Python Version: 3.9.2 (default, Mar 12 2021, 04:06:34) [GCC 10.2.1 20210110]
Uptime: 14 Days, 6 Hours, 52 Minutes, 50 Seconds

Expecting a crash of domoticz in the coming hours....

Process memory usage of 100MB should not crash your system. What other processes are running on your system?

There are other processes running on the system (otmonitor, nodered, mosquito MQTT, monit) but they all keep running. Only domoticz crashes and is restarted by monit every once in a while after the used memory of the domoticz process has increased to around 75 - 85 Mb. I did not have this behaviour with previous 2023.x installations.

When I desactivate Dzvents scripts in domoticz parameters, memory stop increasing...(!) but none of my dzvents scripts seems wrong :\