Likwid H-Craft wrote:oh and Adam is it a, bug when minetest close without you closing it?
It happen to me and, I didn't get to save what I was making.
Inocudom wrote:I saw something in the commits to the git version of Minetest that dealt with fixing a memory leak. Was this leak the cause of the increase in RAM and CPU usage after 0.4.5 stable? Memory leaks can be a serious problem, so it is a good thing that something was done about the one in Minetest.
PilzAdam wrote:Inocudom wrote:I saw something in the commits to the git version of Minetest that dealt with fixing a memory leak. Was this leak the cause of the increase in RAM and CPU usage after 0.4.5 stable? Memory leaks can be a serious problem, so it is a good thing that something was done about the one in Minetest.
People are working to fix even bigger memory leaks.
And 0.4.6 uses less RAM and CPU because the code was improved.
Likwid H-Craft wrote:Hey how do you make a build work? like how you make the source code files gone, and have a .exe?
Inocudom wrote:I am curious about the commit involving system-wide LuaJIT. What exactly does this mean and what must we do to prepare our computers for it? Might as well ask now so that questions can be avoided when the next build comes out.
libluajit-5.1-common libluajit-5.1-2 libluajit-5.1-dev
cmake . -DLUA_INCLUDE_DIR=path/to/lua/headers -DLUA_LIBARY=luajit.lib
jojoa1997 wrote:With your most current build when I get an error minetest shutdown instead of going to debug screen.
PilzAdam wrote:1f42479-bugfixes
Inocudom wrote:It has been a long time since the last time you made a build, PilzAdam. Development on Minetest seems to be slow lately.
PilzAdam wrote:New build: 4a9b8aa-sandy
Some additions to API, some new nodes, new textures and other stuff.
Users browsing this forum: No registered users and 7 guests