When I open FreeFlow Core in my web browser I'm getting a Warning at the top of the screen that says "Warning: Memory is Low - Less Than 24% Remaining". Can anyone tell me how to find a solution for this? Free up more memory?
FFCore has a monitoring subsystem that tracks memory, disk space and DB table space to ensure there are enough resources for successful job processing.
Memory should free up automatically as jobs complete processing. If this happens chronically, I would suggest you look into increasing the amount of memory in the FFCore server.
You will want to use the Details Tab in Task manager to see system background tasks that may be using memory. Windows will aggressively use available memory for indexing and background tasks when user tasks leave it available. But, the moment a user task needs that memory, it will be freed up. So unless you are seeing a problem, I would not worry about 50% usage.
You can manually kill some process in order to fix this issue. I faced same issue in past after creating an image using graphic design software. I faced that thing only and it got fixed. I guess your issue will be fixed too.
Normally when we get this message, It looks like you have a database space issue. If the disk space is critically low then you can try going into your completed jobs queue and delete your files and other stuff there. It will not affect files that are on your printer and eventually, you can manage to get more space. I hope this will help you.
I appreciated what you said. Can you describe me more about that? It will help me and as well as others.
Thanks for making this thread.
You have an OS driver of some kind that wants a large block of consecutive physical RAM. But it can't get it because all of the physical RAM has been fragmented over time. And because the swap file is disabled it cannot do a RAM defragment.
We usually try to stay current with patches and such, so reboots of the server happen about once a month for us. That said there was a time when the FFC server didn't get that attention, and we saw this message pop up. A reboot was all that was necessary.