Error: crash due to MeshUpdate, bad allocation, debug stack

Post Reply
anuser
Member
Posts: 22
Joined: Sun May 01, 2016 23:07

Error: crash due to MeshUpdate, bad allocation, debug stack

by anuser » Post

I would like to ask what I can do? Game crash just after loading, no gameplay possible. That is happening only when I run the game with different than default textures. What is wired, a few hour earlier there was no such error! I have do nothing with the game config, modding or whatever.

Win 7, minetest Krock's 32-bit MSVC 0.4.14

Code: Select all

2016-05-27 15:23:33: ACTION[Server]: singleplayer joins game. List of players: singleplayer
2016-05-27 15:23:38: WARNING[Server]: active block modifiers took 221ms (longer than 200ms)
2016-05-27 15:23:38: ERROR[MeshUpdate]: An unhandled exception occurred: bad allocation
2016-05-27 15:23:38: ERROR[MeshUpdate]: In thread 1428:
2016-05-27 15:23:38: ERROR[MeshUpdate]: e:\programme\mt_compiler\minetest\src\util/thread.h:e2: UpdateThread::run: A fatal error occured: bad allocation
2016-05-27 15:23:38: ERROR[MeshUpdate]: Debug stacks:
2016-05-27 15:23:38: ERROR[MeshUpdate]: DEBUG STACK FOR THREAD b8c: 
2016-05-27 15:23:38: ERROR[MeshUpdate]: #0  EmergeThread::run
2016-05-27 15:23:38: ERROR[MeshUpdate]: DEBUG STACK FOR THREAD e84: 
2016-05-27 15:23:38: ERROR[MeshUpdate]: #0  main
2016-05-27 15:23:38: ERROR[MeshUpdate]: #1  Client::step
2016-05-27 15:23:38: ERROR[MeshUpdate]: #2  Client::ReceiveAll
2016-05-27 15:23:38: ERROR[MeshUpdate]: #3  Client::Receive
2016-05-27 15:23:38: ERROR[MeshUpdate]: #4  Client::ProcessData
2016-05-27 15:23:38: ERROR[MeshUpdate]: DEBUG STACK FOR THREAD 1274: 
2016-05-27 15:23:38: ERROR[MeshUpdate]: #0  ServerThread::run
2016-05-27 15:23:38: ERROR[MeshUpdate]: #1  Server::Receive
2016-05-27 15:23:38: ERROR[MeshUpdate]: DEBUG STACK FOR THREAD 1428: 
2016-05-27 15:23:38: ERROR[MeshUpdate]: #0  UpdateThread::run
2016-05-27 15:23:38: ERROR[MeshUpdate]: DEBUG STACK FOR THREAD 169c: 
2016-05-27 15:23:38: ERROR[MeshUpdate]: #0  UpdateThread::run

User avatar
Fixer
Member
Posts: 900
Joined: Sun Jul 31, 2011 11:23
IRC: Fixer
In-game: Fixer
Location: Ukraine

Re: Error: crash due to MeshUpdate, bad allocation, debug st

by Fixer » Post

Try 64bit version, may be low on memory.

User avatar
Krock
Developer
Posts: 4596
Joined: Thu Oct 03, 2013 07:48
GitHub: SmallJoker
Location: Switzerland
Contact:

Re: Error: crash due to MeshUpdate, bad allocation, debug st

by Krock » Post

The higher your texture pack resolution is, the more RAM it will use. Also meshes and sounds will make it worse and cause this out-of-memory problem after playing for a while.
Either use a 64-bit binary (if possible) or get a texture pack with a lower resolution.
Look, I programmed a bug for you. >> Mod Search Engine << - Mods by Krock - DuckDuckGo mod search bang: !mtmod <keyword here>

anuser
Member
Posts: 22
Joined: Sun May 01, 2016 23:07

Re: Error: crash due to MeshUpdate, bad allocation, debug st

by anuser » Post

Thanks Fixerol and Krock for your answers.

If it is due to RAM it could explain why that crash do not show on a regular basis. Maybe it happened when other programs want more RAM for them. I use Windows, so that should be nothing new that there is always a thousand of system services that start in inappropriate time. Let consider just onue stupid thing like Windows Update. It need many, many RAM and that it can make a conflict with RAM demand from the game. I know, that is naive, but thinking in that way first I look with Process Explorer on what is going on, kill all RAM eaters and then run the game. That crash still happening, but much rare. In most cases killing Windows Update before minetest running lowered the frequency of error reported here and made the gameplay much longer.

But I still think that those errors cannot be explained just with small RAM resources in player computer. Sometimes I use much more RAM demanding programs, and they do not have any out of memory errors and those programs do not crash surprisingly with some random error reporting in logs. I even do not belive that in that time when minetest crash there is some RAM lacking in the system. But so what, I do nothing with that problem, I can just try to survive with minetest to have some gameplay fun, lol.
Krock wrote:The higher your texture pack resolution is, the more RAM it will use. Also meshes and sounds will make it worse and cause this out-of-memory problem after playing for a while.
So I would like to ask how to disable sounds? And what to do with meshes, whatever they are?
Krock wrote:Either use a 64-bit binary (if possible) or get a texture pack with a lower resolution.
Second sound great, I can use only selected textures of interest with higher resolution and the others can be the lowest. But the 64bit version is known to make out of memory crash much often than 32-bit version. I know that very well. With this new minetest I can only use 32-bit version. 64-bit is not playable for me. It crash all the time jus as the world load.

User avatar
azekill_DIABLO
Member
Posts: 7502
Joined: Wed Oct 29, 2014 20:05
GitHub: azekillDIABLO
In-game: azekill_DIABLO
Location: OMICRON
Contact:

Re: Error: crash due to MeshUpdate, bad allocation, debug st

by azekill_DIABLO » Post

which windows do you use??for me i can't put gigantic textures when on Win10 but it kinda slow on 7

Post Reply

Who is online

Users browsing this forum: 2bad and 2 guests