Page 1 of 1
Minetest crashes, digging too deep perhaps?
Posted:
Sun Jun 03, 2012 05:31by ruler01
version minetest: minetest-0.4.dev-20120408-win32
here is a screenshot when it crashes
some of the last lines in debug.txt
Your phone or window isn't wide enough to display the code box. If it's a phone, try rotating it to landscape mode.
- Code: Select all
13:27:15: INFO[main]: Client::addUpdateMeshTaskForNode(): (-127,-389,77)
13:27:15: INFO[main]: Client::addUpdateMeshTaskForNode(): (-127,-389,77)
13:27:15: VERBOSE[main]: OpenALSoundManager::maintain(): 6 playing sounds, 14 sound names loaded
13:27:15: VERBOSE[main]: OpenALSoundManager::maintain(): deleting 2 playing sounds
13:27:15: INFO[main]: OpenALSoundManager: Creating playing sound
13:27:15: INFO[main]: Pointing at [node under=-127,-390,77 above=-127,-389,77]
13:27:15: VERBOSE[ServerThread]: TOSERVER_INTERACT: action=2, item=0, pointed=[node under=-127,-389,77 above=-127,-388,77]
node_dig
13:27:15: ACTION[ServerThread]: singleplayer digs default:stone at (-127,-389,77)
13:27:15: VERBOSE[ServerThread]: Server: MapEditEvents:
13:27:15: VERBOSE[ServerThread]: MEET_REMOVENODE: - - - - - - - - - - - - 1
13:27:15: INFO[main]: Client::addUpdateMeshTaskForNode(): (-127,-389,77)
13:27:15: INFO[main]: Started digging
13:27:15: INFO[main]: Client::addUpdateMeshTaskForNode(): (-127,-390,77)
13:27:15: VERBOSE[ServerThread]: TOSERVER_INTERACT: action=0, item=0, pointed=[node under=-127,-390,77 above=-127,-389,77]
13:27:15: VERBOSE[main]: OpenALSoundManager::maintain(): 5 playing sounds, 14 sound names loaded
13:27:15: VERBOSE[main]: OpenALSoundManager::maintain(): deleting 2 playing sounds
13:27:15: INFO[main]: OpenALSoundManager: Creating playing sound
13:27:15: VERBOSE[main]: OpenALSoundManager::maintain(): 4 playing sounds, 14 sound names loaded
13:27:15: INFO[main]: OpenALSoundManager: Creating playing sound
13:27:15: VERBOSE[main]: OpenALSoundManager::maintain(): 5 playing sounds, 14 sound names loaded
13:27:15: INFO[main]: OpenALSoundManager: Creating playing sound
13:27:15: VERBOSE[main]: OpenALSoundManager::maintain(): 6 playing sounds, 14 sound names loaded
13:27:15: VERBOSE[main]: OpenALSoundManager::maintain(): deleting 1 playing sounds
13:27:15: INFO[main]: OpenALSoundManager: Creating playing sound
13:27:15: INFO[main]: Digging completed
13:27:15: INFO[main]: Client::addUpdateMeshTaskForNode(): (-127,-390,77)
13:27:15: INFO[main]: Client::addUpdateMeshTaskForNode(): (-127,-390,77)
13:27:16: VERBOSE[main]: OpenALSoundManager::maintain(): 6 playing sounds, 14 sound names loaded
13:27:16: VERBOSE[main]: OpenALSoundManager::maintain(): deleting 3 playing sounds
13:27:16: INFO[main]: OpenALSoundManager: Creating playing sound
13:27:16: INFO[main]: Pointing at [node under=-127,-391,77 above=-127,-390,77]
13:27:16: INFO[main]: Started digging
13:27:16: INFO[main]: Client::addUpdateMeshTaskForNode(): (-127,-391,77)
In trans_func.
13:27:47: INFO[EmergeThread]: on_generated took 32053ms
Posted:
Sun Jun 03, 2012 06:34by cosarara97
I don't know what's the problem, but you aren't digging too deep.
Posted:
Sun Jun 03, 2012 08:41by Calinou
It works fine for me. What's your computer specs (CPU/RAM/graphics card) ? Windows version?
Posted:
Sun Jun 03, 2012 09:29by Jordach
All that may have happened is; Minetest "failed" generating caves.
See that last line on this:
Your phone or window isn't wide enough to display the code box. If it's a phone, try rotating it to landscape mode.
- Code: Select all
13:27:47: INFO[EmergeThread]: on_generated took 32053ms
Posted:
Sun Jun 03, 2012 11:02by babe223
happens to me when I turn the game otherwise the texture is bugged or whether it is white in the other versions that did not happen
Posted:
Sun Jun 03, 2012 14:35by ruler01
Calinou wrote:It works fine for me. What's your computer specs (CPU/RAM/graphics card) ? Windows version?
kinda low spec laptop
CPU = 1.2GHz dual core
RAM = 4GB
Graphics card = intel
Windows version = Windows 7 32-bit
Jordach wrote:All that may have happened is; Minetest "failed" generating caves.
See that last line on this:
Your phone or window isn't wide enough to display the code box. If it's a phone, try rotating it to landscape mode.
- Code: Select all
13:27:47: INFO[EmergeThread]: on_generated took 32053ms
Minetest failed generating caves? what have i done :O
Posted:
Thu Aug 02, 2012 17:09by The_SanaM
I have same problem, and now cannot play that map because it crashes right away. How to solve?
Posted:
Thu Aug 02, 2012 17:25by Topywo
What mods have you installed?
Posted:
Thu Aug 02, 2012 17:46by The_SanaM
Mesecons, moreores, hydroculture, tweaked bed, and bookmarks, they all worked until I went down to -580 something, then the game crashed and now any time I attempt to go into the map it crashes, it was my best map too:(
Posted:
Thu Aug 02, 2012 18:06by Topywo
Take out the moreores mod and try again. If that doesn't work, take the mesecons out etc.etc. until you can go up again.
p.s. you can always reinstall the mods
Posted:
Thu Aug 02, 2012 18:20by The_SanaM
Okay I will try that
Posted:
Thu Aug 02, 2012 18:25by The_SanaM
I took out all mods, and it has same problem...
Posted:
Thu Aug 02, 2012 18:36by The_SanaM
A message that comes up in the side thing is "The application has requested the Runtime to terminate it in an unusual way. Please contact the application's support team for more information."
Posted:
Thu Aug 02, 2012 19:38by Topywo
I tried to crash with moreores and gems, but didn't manage to.
Maybe this is a Windows 7 problem, idk.
Maybe there is some information in your debug.txt (you could rename the present, make a new file called debug.txt, try minetest and then open the debug.txt file to look what's in it (the errors, work your way up from the bottom of the text to find the errors). A new debug.txt, because the old one is probably full. My debug.txt just stops taking new info...
If you succeed to enter the game and are able to type for a second, try typing "/grant singleplayer all" and then teleporting away "/teleport 0,10,0".
Posted:
Thu Aug 02, 2012 19:39by The_SanaM
Okay thank you for help I will try all of these things then tell you what has happened.
EDIT: I made new debug file and same thing occurred. I found one thing in the file that said ERROR
14:43:39: INFO[EmergeThread]: WARNING: Database read statment failed to prepare: disk I/O error
14:43:39: ERROR[EmergeThread]: ERROR: An unhandled exception occurred: Cannot prepare read statement
Not sure if that has anything to do with it though
Posted:
Fri Aug 03, 2012 13:39by cae2000
make sure your hdd isnt full and that you have all your files are in minetest.
EDIT: you could have ran out of ram too.
Posted:
Fri Aug 03, 2012 14:07by Jordach
The_SanaM wrote:Your phone or window isn't wide enough to display the code box. If it's a phone, try rotating it to landscape mode.
- Code: Select all
14:43:39: INFO[EmergeThread]: WARNING: Database read statment failed to prepare: disk I/O error
14:43:39: ERROR[EmergeThread]: ERROR: An unhandled exception occurred: Cannot prepare read statement
This looks like a:
1) Highly fragmented hard disk.
2) Too many file operations on the disk that Minetest is located on.
3) The RPM (Hard Drive spin speed) number is either too low for your kind of mining.
4) Damaged hard disk sectors.
5) Unknown.
Posted:
Fri Aug 03, 2012 14:37by The_SanaM
Reading these suggestions I believe that this problem is the RPM number is too low for how deep I am digging. I started a new map and that one works just fine, so it has everything to do with the space and the amount it has to load mining that deep down.
EDIT: I just went onto Minetest for the first time today, and surprisingly enough the map loaded! I don't thing that I will return to those depths tho but I am very happy that somehow it worked its self through.
Now that I think about it, I probably should've shut off my computer then retried...Never thought about that. Anyways thank you all for your suggestions.