05-16-2020, 01:21 AM
(This post was last modified: 05-16-2020, 01:21 AM by Alexandre Machado.)
"Out of system resources" most of the times is caused by errors in code where the size of a buffer in a memory allocation routine is wrong, e.g. instead of trying to allocate a small (e.g. 1 kb) buffer, a random number is passed to, for instance, GetMem() as the size of the buffer. Once that random number can be anything, it is very likely that it represents a huge number and the memory allocation fails with that exactly error message.
According to your description I don't think it is caused by memory leaks (the whole application fails, and a new login would also fail).
First you need to find out where this happens.
I strongly suggest you enable IW error log. You can read how to do it here:
http://docs.atozed.com/docs.dll/developm...ogger.html
Once the error happens again, you will have a detailed log file containing the call stack. That's how you start trying to find where the problem is.
According to your description I don't think it is caused by memory leaks (the whole application fails, and a new login would also fail).
First you need to find out where this happens.
I strongly suggest you enable IW error log. You can read how to do it here:
http://docs.atozed.com/docs.dll/developm...ogger.html
Once the error happens again, you will have a detailed log file containing the call stack. That's how you start trying to find where the problem is.