For quite a few versions now I have been hitting a memory leak.
Is this a known issue?
Any idea how to track it down?
Below you can see how much memory BI uses. It was fine until I upgraded from a very old version to a new version. As you can see, its been a problem since. Also, I only have 3 cameras on this system.
.
memory leak 5.5.1.18
Re: memory leak 5.5.1.18
Just curious, what is your server environment? Is it a VM? What hypervisor? What OS is your server?
I too have a memory leak though not anywhere near as severe as yours looks. I don't have the link handy but I've seen a forum topic that does reference memory leak issues when running on a VMware hypervisor.
I too have a memory leak though not anywhere near as severe as yours looks. I don't have the link handy but I've seen a forum topic that does reference memory leak issues when running on a VMware hypervisor.
Blue Iris 5.9.9.x | Server 2025 VM | Xeon E5-2660 v3 @ 2.60GHz - 32 Cores | 48GB RAM | 8TB RAID | Sophos UTM WAF | Mostly various SV3C Cameras
Re: memory leak 5.5.1.18
Have you down the normal things like making sure your fps and iframe settings match, trying h264 if the cams are set to h265, disabling hardware acceleration if you have it enabled or even trying a different variant?
I used to use intel Beta but have recently changed to intel VPP as the beta was causing issues.
I used to use intel Beta but have recently changed to intel VPP as the beta was causing issues.
Re: memory leak 5.5.1.18
5.5.1.19 is out. Upgrade and see if that resolves the issue.
Re: memory leak 5.5.1.18
19 also leaks.
Re: memory leak 5.5.1.18
20 supposedly fixes it but I’ve not tried it yet.
Re: memory leak 5.5.1.18
I also had the same issue with 5.5.X.X. I've had to go back to 5.4.9.18. I've tried multiple 5.5 versions and all seem to have isssues. Going back to 5.4 seems to resolve all my problems. Ticket to Blue Iris support and they told me I was the only one that reported this issue.
My workaround........ I created a powershell script to restart the Blue Isis service twice a day. That would free up the memory again.
In the end, I went back to 5.4.9.18.
My workaround........ I created a powershell script to restart the Blue Isis service twice a day. That would free up the memory again.
In the end, I went back to 5.4.9.18.
Re: memory leak 5.5.1.18
For those that use deepstack there is a fix in 5.5.2.0 where the deep stacks process is a child process of BI so if BI is stopped or crashes then when BI stops it should also stop any child processes.
Apart from one version from 5.5.1.x I didn’t really see any issues with memory leaks but then again I don’t use deepstack. What I have noticed is that the overall memory usage has increased, my rig used to average around 24% but with the recent releases it now sits at around 31%.
Apart from one version from 5.5.1.x I didn’t really see any issues with memory leaks but then again I don’t use deepstack. What I have noticed is that the overall memory usage has increased, my rig used to average around 24% but with the recent releases it now sits at around 31%.