I was on 5.6.1.3 when the issue was happening. However, yesterday I upgraded to 5.6.2.10 and so far the issue hasn't repeated (but it's been less than 48 hours).
Overallocated Storage error every few days?
- Thread starter Post
- Start date
I was on 5.6.1.3 when the issue was happening. However, yesterday I upgraded to 5.6.2.10 and so far the issue hasn't repeated (but it's been less than 48 hours).
After more checking, I've discovered that Blue Iris suffered a memory leak during the span of this event.
The logfile errors may just be something that happens during a memory leak.
[Chart made using Google Charts on a CSV log managed by Blue Iris 'write to file' actions. Red datapoints (‘Status’) show RAM values on Blue Iris restarts.]
The logfile errors may just be something that happens during a memory leak.
[Chart made using Google Charts on a CSV log managed by Blue Iris 'write to file' actions. Red datapoints (‘Status’) show RAM values on Blue Iris restarts.]
Last edited:
I don't know how to determine RAM usage after the fact.
You can monitor usage in real time using Task Manager > Performance tab > Resource Monitor. But you need to catch the leak "in the act".
You can create your own log pretty easily as follows:
This logs the following values every 6 minutes (10x per hour): Timestamp, SoftwareUsedRAM, Uptime, RAM_Pct, Tag. A new file is created monthly.
I use a custom web app to visualize the data, but you can use Excel to import, view, and chart the resulting CSV data files.
You can monitor usage in real time using Task Manager > Performance tab > Resource Monitor. But you need to catch the leak "in the act".
You can create your own log pretty easily as follows:
This logs the following values every 6 minutes (10x per hour): Timestamp, SoftwareUsedRAM, Uptime, RAM_Pct, Tag. A new file is created monthly.
I use a custom web app to visualize the data, but you can use Excel to import, view, and chart the resulting CSV data files.
Last edited:
Flintstone61
Known around here
the motherfucking default for alerts is 20Gb (I think) cuz i didn't mess with it ( i don't think)
why is the living bloody heel is your alerts size downsized to 1GB?
why is the living bloody heel is your alerts size downsized to 1GB?
Flintstone61
Known around here
Flintstone61
Known around here
Flintstone61
Known around here
Flintstone61
Known around here
Thanks...Very cool! I went ahead created the memory log and this is what I got for a 24 hour period. Doesn't look like a memory leak.
Interestingly, I have still not experienced the storage error again since upgrading to 5.6.2.10 this past Sunday. Keeping my fingers crossed!
Now that you are continuously updating the CSV file, you can look back any time for possible leak events.
Regarding your chart, suggest manually scaling the vertical axis from a minimum = 0 to a maximum = your system memory. This will eliminate the ‘noise’. Leaks will jump out.
Regarding your chart, suggest manually scaling the vertical axis from a minimum = 0 to a maximum = your system memory. This will eliminate the ‘noise’. Leaks will jump out.