repetitivestrain wrote: ↑Sun Feb 01, 2026 10:54
ArceusI wrote: ↑Sun Feb 01, 2026 06:41
None of this fixes the underlying poor stability of MineClonia in general. In fact, it likely made it worse because now the coding is going to get too complicated for Luanti on even 4GB RAM to handle. Pushing the minimum to 5GB RAM. There needs to be emergency patches in order to restore stability for weaker devices, or users will likely flee back to VoxeLibre, which is a lot more stable on said devices. This particularly affects Android & iPad (if applicable) users.
Memory consumption is in no wise connected to stability, and neither is Mineclonia's excessive.
Code: Select all
USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND
minetest 2485672 1.3 12.4 1700M 989M ? Ssl 06:59 4:02 luantiserver
Before this server was restarted for updates, it was online for in excess of 1 month.
Anyway, if you don't report the backtraces of crashes to us, but simply post deceptive and affected protests, which contribute nothing at all to their resolution, you cannot expect them to be addressed. As you have been informed on numerous occasions, of which I hope this will be the last. (And I also urge other players to take this member's comments with skepticism, considering how much he has been guilty of hyperbole as of late...)
If Luanti itself crashes, no log can be made, and I could try exploiting a feature of Android that can reveal what causes crashes. But, it wouldn't match what this Forum expects when it comes to code. I use my T901, which has 4GB RAM, and when MineClonia runs long enough, it forces Luanti to crash outright, kicking me to the OS screen & killing the Luanti process. I suspect a RAM leak.
A case in point for the RAM/Stability link is Donkey Kong 64, from 1999. If you play the game non-stop for 10 hours, the RAM is used up completely, and it begins overwriting used RAM, which causes stability problems, and eventually it crashes. This seems to also happen with MineClonia, but because of Luanti's RAM requirements, when MineClonia starts to overload, it easily overwrites a piece of RAM that Luanti needs, and it kills the app to prevent corruption. That's my assumption.