But after trainied in C++, Oracle, network and html + learn php in 200-2005, I quit my job and moved in another country ... whatever, and some basics of this old knowledge not changed yet.
* No computer run without memory
* every code, whatever it does uses/consumes memory
so depending on my research in low Lua memory, there is another fact I read
* 64 systems only give Lua/JIT 2 GB of ram,
* what is, depending on the system and code and version of lua and also not started at beginning, so that the we had the issue that OOM errors available memory are from just 14 MB up to my reported 1300 MB.
So for clear, a [Mod] uses memory as it is loaded via its init.lua by set true in world.mt file, and the problem yet was, we had no Idea which mod uses how much (? solved ?), or further which one gains more (unsolved).
So depending on my tick to ask after every loaded [Mod] the used lua mem with collectgarbage() (see thread)
and found out some very hungry mods listed there.
So with this evidence in consumption I made an issues at the 3 main programmers and got an answer.
As I said before, moretrees does not use a significant amount of memory. It's up to the engine to decide what to use and what not to. Hell, the whole Dreambuilder modpack (which includes moretrees) is only 60 MB.
If you're running short on memory, get more.
So take a few facts:
* if I false this mod, mod will not load, mod will not consume memory !
mean, it is the code of the mod, the decision of the programmer, wanted to load data = use memory and responsible for that
-- sure it is my decision if i use this mods, but when it keeps like this, and I wanna use Luajit, then some mods will be out, and after I can proof that it runs then without OOM, sure I will issue an warning for this mods together with LuaJIT using ...
* the engine is just doing what is coded in the mod, the engine does nothing load with out the code, belong to the code, as this is why after loading init.lua more memory of the available lua mem is used.
* yes getting more memory, by jump back to 32bit lua might help = 4 GB, if I am right,
-- sure the other solution is find out optimising Lua memory, getting more mem, or using better start position (waiting for LUA code upgrade)
So your meaning, better facts ... about this story here ...