Quote:
Originally Posted by staaat
A question for you when you managed to reproduced the issue, was this on a machine that had more than 4GB of memory? what I found was that when I received the OOM error, there was still plenty of memory available to use - it was just stopping at the 4GB usage with OOM error.
|
My server had 128GBs of RAM, so it would have plenty to work from. I don't recall any parameter or setting to increase the limit, but maybe someone else recalls such a thing.
Quote:
Originally Posted by staaat
A question you might not be able to answer? but why is having a deviation of 90 seconds causing the OOM error when there is still plenty of memory available to use! Maybe a question for Valve?!
|
The deviation in time increases the amount of RAM used when increasing between the two. The RAM used increases depending on how far away GOTV1 is from original GOTV, regardless of the starting point.
Unfortunately I can't answer your question of why, as I don't know at this moment.