The last few days, lots of game crashing errors.

[TExtubation]

Me and one other person I know, for the last couple of days, have been getting very random game crashing errors that we cannot pin down. 1 in 5 attempts to start the game succeed, but other seemingly random occurrences cause that game to ultimately crash. These include simply clicking on a menu option, clicking "Play Game", in the middle of a game loading, trying to press esc to bring up the in game menu, and even when trying to exit to menu.

The debug log shows the following for most errors:

2023-05-22 07:50:25: [Main]: Automatically selecting world at [/home/nightstalker/void/appimage/minetest/minetest/Minetest-5.7.0-x86_64/Minetest-5.7.0-x86_64.AppImage.home/.minetest/worlds/test]
2023-05-22 07:50:26: WARNING[Main]: Could not load icon file '/usr/local/share/icons/hicolor/128x128/apps/minetest.png'
2023-05-22 07:50:26: ERROR[Main]: In thread 7f683fe683c0:
2023-05-22 07:50:26: ERROR[Main]: /tmp/minetest/src/script/cpp_api/s_base.cpp:54: ScriptApiBase::ScriptApiBase(ScriptingType): A fatal error occurred: luaL_newstate() failed

And then sporadically for these entries:

2023-05-22 07:50:22: [Main]: Automatically selecting world at [/home/nightstalker/void/appimage/minetest/minetest/Minetest-5.7.0-x86_64/Minetest-5.7.0-x86_64.AppImage.home/.minetest/worlds/test]
2023-05-22 07:50:23: WARNING[Main]: Could not load icon file '/usr/local/share/icons/hicolor/128x128/apps/minetest.png'
2023-05-22 07:50:23: ERROR[Main]: GUIEngine: execution of menu script failed: Failed to load and run script from /tmp/.mount_MineteMimoJk/usr/bin/../builtin/init.lua:
2023-05-22 07:50:23: ERROR[Main]: not enough memory
2023-05-22 07:50:23: ERROR[Main]: stack traceback:
2023-05-22 07:50:23: ERROR[Main]:   [C]: in function 'dofile'
2023-05-22 07:50:23: ERROR[Main]:   ....mount_MineteMimoJk/usr/bin/../builtin/mainmenu/init.lua:44: in main chunk
2023-05-22 07:50:23: ERROR[Main]:   [C]: in function 'dofile'
2023-05-22 07:50:23: ERROR[Main]:   /tmp/.mount_MineteMimoJk/usr/bin/../builtin/init.lua:63: in main chunk
2023-05-22 07:50:23: ERROR[Main]: No future without main menu!

2023-05-22 07:50:28: [Main]: Automatically selecting world at [/home/nightstalker/void/appimage/minetest/minetest/Minetest-5.7.0-x86_64/Minetest-5.7.0-x86_64.AppImage.home/.minetest/worlds/test]
2023-05-22 07:50:28: WARNING[Main]: Could not load icon file '/usr/local/share/icons/hicolor/128x128/apps/minetest.png'
2023-05-22 07:50:33: ERROR[Main]: Main menu error: OOM error from mod '??' in callback handleMainMenuButtons(): not enough memory
2023-05-22 07:50:33: ERROR[Main]: Current Lua memory usage: 0 MB
2023-05-22 07:50:33: ERROR[Main]: In thread 7f4d7dccd3c0:
2023-05-22 07:50:33: ERROR[Main]: /tmp/minetest/src/script/cpp_api/s_base.cpp:54: ScriptApiBase::ScriptApiBase(ScriptingType): A fatal error occurred: luaL_newstate() failed

2023-05-22 07:46:58: [Main]: Automatically selecting world at [/home/nightstalker/void/appimage/minetest/minetest/Minetest-5.7.0-x86_64/Minetest-5.7.0-x86_64.AppImage.home/.minetest/worlds/test]
2023-05-22 07:46:59: WARNING[Main]: Could not load icon file '/usr/local/share/icons/hicolor/128x128/apps/minetest.png'
2023-05-22 07:46:59: ERROR[Main]: Execution of async base environment failed: Failed to load and run script from /tmp/.mount_MineteCnjGLn/usr/bin/../builtin/init.lua:
2023-05-22 07:46:59: ERROR[Main]: not enough memory
2023-05-22 07:46:59: ERROR[Main]: stack traceback:
2023-05-22 07:46:59: ERROR[Main]:   [C]: in function 'dofile'
2023-05-22 07:46:59: ERROR[Main]:   /tmp/.mount_MineteCnjGLn/usr/bin/../builtin/init.lua:42: in main chunk
2023-05-22 07:46:59: ERROR[Main]: In thread 7f175c0503c0:
2023-05-22 07:46:59: ERROR[Main]: /tmp/minetest/src/script/cpp_api/s_async.cpp:fe: bool AsyncEngine::prepareEnvironment(lua_State*, int): A fatal error occurred: Execution of async base environment failed

There seems to be no rhyme or reason to these errors as they can happen at any time. And yes even though most of these say "not enough memory" minetest is only using a few hundred MB at most of my 16GB when these things occur.

There was an update on our systems right before these issues started, but we have yet to figure out what could have changed that affected the minetest appimage so much (even older versions). All of my other non-minetest appimages appear to be functioning properly.

Minetest 5.4.0 will not start at all giving "Irrlicht: Could not create GLX rendering context" errors (I know this is really old but I wanted to include it for completeness) Version 5.5.0 seems to start 2 out of 5, but when it does crash it will error out with "not enough memory" errors While 5.6.0, 5.6.1, 5.7.0 show the above posted errors with no discerning pattern.

Any help would be greatly appreciated.

"UPDATE" 06/07/23 - Do not know which system update created the issue, but another update fixed the issue as well. Absolutely have no idea what would have affected this appimage and none of the others I use. Void linux.

[An0n3m0us]

Hello there, sorry for the late reply; full-time job plus university are taking up a lot of my time. This is definitely very strange.... how is it with Minetest's official AppImages? The issue seems to have some relation to #12... did you manage to solve it in the end?

[Firestar-Reimu]

Please try this https://gitlab.com/minetest/minetest/-/jobs/4096592257/artifacts/download?file_type=archive

[TExtubation]

Around 06/07/2023 there was another big update on Void Linux and the issue seemed to resolve itself at that time for the appimage. My son, on the other hand, did not want to wait for anything and almost immediately (upon having said issues) installed the Void repo version of Minetest. Once the repo version was installed on his system the appimage started to work perfectly for him again. As a test, I uninstalled the repo version and everything that installed with it on his machine, and again the appimage version started having issues like before. So, unfortunately I have no idea what dependency caused this issue, but as of right now, since the update around the 7th of June, the appimage is functioning perfectly again for us. I'm sorry I couldn't pin anything more specific down to help, other than what I've already written.

And from the both of us, we wanted to thank you for the work you do to make this appimage.

[An0n3m0us]

I see hmm, the update solved it... ahh, that's okay; if it ever re-occurs, feel free to re-open this issue. I'm glad to hear you are both finding benefit using it, and you're both welcome :)