Okay it feels like I am onto something.. Here is what I am finding now at-least with my .17
When I click on a camera which has sub stream as it switches to main stream seems like blueiris holds more ram and never let go off it.. and to my theory I click on bunch of cams to see view screen and back and fourth so far I have racked up.
Good catch! I can confirm that I have the same situation with my set up. It doesn't matter how I view the cameras... UI3, BI client or iOS app, the memory bumps up each time a camera is viewed and never gets released. I also made Ken aware.
I have to admit I am seeing memory creep as well and I'm using sub streams on 13 out of 15 cameras at the moment. Up about 2 gigs in the last 12 hours running on Nvidia and version .17 for BI.
Edit - Just single viewed a camera in UI3 and played a clip while watching memory on the app. Memory went up with the view and playback but returned after I closed that out
Update - Ken did check my PC as per Ken this is normal seems like for my camera load. He said when all cam is viewed I use about 16gb of ram for Blueiris Alone.. I guess its good I have 64 GB of ram..
I just thought once I am done viewing Blueiris will let that ram go or free up
I guess that is not the case and its normal. which is fine I guess as I have ram to spare.
But moving forward I guess we all should have some ram to spare if we have more high load cams ..
I'm running 32gb of dual channel so I guess I'm OK for a while yet. I have yet to see BI go past about 6gb so I'm not too worried. Something to keep an eye on though just in case
This systems ram will creep until it locks up the computer in 30 hrs, using 90% of ram, even if:
No one looks at a camera feed during that time.
No one use's UI3.
No one connects with the BI app.
Console is closed during that time, just running the service.
This system has 8 cams, all 2mp, 15fps, running H265, at 2048 bit rate.
Approx 41MBps total.
My system here at home, does not have any of these memory issue's on the same ver.
I'm still chatting with Ken. This is a big problem for me given I travel and will most certainly be checking BI remotely while away. I could do it maybe a dozen times before it would lock up my BI PC.
Yea Mine seems to go up to 16gb as per my load if I were to view all my cam. I just got another email from ken
He said "I'll see about freeing this earlier. "
Again many thanks to BI support to still actively looking into this. Hopefully he can find a way to free this at some point..
Looney does your memory keep growing or does it like stops at certain point. One thing you wanna see is if you disable the camera do you get some of that ram back like try one by one.. Just a thought..
I'm running .17 as well. I saw an interesting thing when I checked first thing this morning. Last night it was showing ~4.6GB of RAM utilization. At 06:30 this morning it was ~3.6BG. Dropped 1GB overnight.
Yea Mine seems to go up to 16gb as per my load if I were to view all my cam. I just got another email from ken
He said "I'll see about freeing this earlier. "
Again many thanks to BI support to still actively looking into this. Hopefully he can find a way to free this at some point..
Looney does your memory keep growing or does it like stops at certain point. One thing you wanna see is if you disable the camera do you get some of that ram back like try one by one.. Just a thought..
Hope BI support team can find a solution for you. I am guessing your bios / drivers are all up to date and I think you even posted earlier try to even roll back the drivers but still same results.
Have you try to run just one cam and disable other and see if there is some particular cam causing it for some weird reason or just disable every cam and let bi run and see if ram keeps going up still ..
Hope BI support team can find a solution for you. I am guessing your bios / drivers are all up to date and I think you even posted earlier try to even roll back the drivers but still same results.
Have you try to run just one cam and disable other and see if there is some particular cam causing it for some weird reason or just disable every cam and let bi run and see if ram keeps going up still ..
How about the stupidest thought, ever? Have you deleted cameras one by one until the issue stops? I've seen Blue Iris do some strange things with camera definitions before. I quit fighting it, and just deleted the danged thing from the application, exited the app, restarted the service, then re-entered the app and re-created the camera. Problem resolved. It's a bit of a pain, but just thought I'd mention it.
FYI, just checked, and RAM usage is just below 5.4 GB tonight.
I just installed 5.3.9.0. I can confirm the Ram issue seems to be resolved where it was not freeing up the ram after live view now it does free up right away..
I just installed 5.3.9.0. I can confirm the Ram issue seems to be resolved where it was not freeing up the ram after live view now it does free up right away..
OK, you cornvinced me to try 9.3.9.0 even though I'm not seeing a lot, if any, memory creep. I've ben watching carefully every time I'm on the console and tracking it in a spreadsheet with date and time. It did peak at over 6GB yesterday afternoon but was back down under 4GB this morning. I was wondering if he has a routine in the database maintenance to clean up memory as well.
I did try with the ptz cam My ram on live went up from 4.49 to 5.57 gb.. After I got to the main grid view ram drop back to 4.49-4.50. Seems like mine is going back fine one thing to see if there are motions and its processing alerts you might see ram go up for that time. Maybe that was happening in your case ?