Yep, same here. Running server that claims to be (./arma3server --version) 1.38.128937

No player can connect. server running on 64bit CentOs

Hi.

I am responding here, because I get the exact same error message, but while playing multiplayer.

I have included the crash files, but mdmp file was not genereated. (arma3-crash.7z)

Interesting is, that everyone on the server experienced severe desych/lag, then my game crashed with the "Arma 3. Out of memory (requested 0 KB)". What is even more interesting, is that my friends game got really laggy, and then he was propelled many kilometers to the ocean(!). His game did not actually crash. He just died in game.

Also, I was running the server myself (on a different dedicated machine). Server was writing logs to stdout, because it was a child progress in a node app, so I don't have full logs any more. I did grab this though that looked really interesting:

ARMA STDERR says: 20:34:52 Matrix is not valid as physx transform!
20:34:52 Matrix is not valid as physx transform!
20:34:52 Matrix is not valid as physx transform!
20:34:52 Matrix is not valid as physx transform!
20:34:52 Matrix is not valid as physx transform!
20:34:52 Matrix is not valid as physx transform!
20:34:52 Matrix is not valid as physx transform!

ARMA STDERR says: 20:34:52 Matrix is not valid as physx transform!
20:34:52 Matrix is not valid as physx transform!
20:34:52 Matrix is not valid as physx transform!
20:34:52 Matrix is not valid as physx transform!
20:34:52 Matrix is not valid as physx transform!
20:34:52 Matrix is not valid as physx transform!
20:34:52 Matrix is not valid as physx transform!
20:34:52 Matrix is not valid as physx transform!
20:34:52 Matrix is not valid as physx transform!

So, something going wrong with the physx definitely sounds like something that might propel people couple kms into the ocean:)

Arma client version 1.36.128579
ArmA Linux Server, ver. 1.36.128579