Fatal: LuaRules: cannot allocate more memory! (805306386 bytes already used, 805306368 bytes maximum)

pandaro commented 8 years ago

for now in nation map (32x32)

eronoobos commented 8 years ago

Sadly, this is only a LuaAI issue. Because of something that's inside an if ShardSpringLua then statement? Because of something in AILoader.lua or preload/shard_lua/? Or because of different garbage collection behaviour between the two environments?

eronoobos commented 8 years ago

https://github.com/eronoobos/BABAR-The-Shardifant/commit/ae5e9eba84734e003b580a283df3c5388d9d3a26 seems to have helped a little, presumably because the table.removes don't leave extra crap sitting around in tables anymore. But still there's something else leaking tons of memory.

eronoobos commented 8 years ago

notes:

With one LuaAI against KAIK, Lua-allocated memory stays around 85 MB for a long time during the mid game. At some point it starts climbing rapidly.
After KAIK has been defeated, Lua memory slowly drops back down to around 85.
If the game is paused, Lua memory drops to around 30. It comes back up if unpaused.
If the game speed is lowered to 1.0, Lua memory stays at around 30.

(data gathered from /debug)

Memory usage therefore indeed seems to be related to garbage collection. I presume that what's left when the game is paused are the Lua tables that are not garbage. Maybe the AI is simply updating tables too often?

eronoobos / BABAR-The-Shardifant

Fatal: LuaRules: cannot allocate more memory! (805306386 bytes already used, 805306368 bytes maximum) #33